Muhammad Ikram Let's talk

Automating a Broken Process Just Breaks It Faster

3 steps, in this order: walk it, cut it, then automate it.

Take a purchase approval. Before anyone builds a workflow, follow one real request from start to finish. Note every signature, every re-typed field, every wait.

Then ask each approver one question: when did you last reject one of these? If the answer is never, that step is a notification, not an approval.

Automate what is left.

Which approval in your company would not survive that question?

01 / 01Automation

Before you automate an approval workflow

Walk it. Cut it. Then automate.

1

Walk one real request

Follow a purchase request from start to finish. Note every signature, re-typed field and wait.

2

Cut what adds nothing

A sign-off that never says no is only a notification.

3

Automate what is left

Fewer steps to build, test and maintain.

Ask every approver: when did you last say no?

More insights

Keep reading

All posts
Carousel

Startups & Product 1 min read

The Fastest Growth Test Is the Feature You Cut

A common trap: the MVP ships with ten features, conversion moves, and nobody can say which one did it. Name the one job, write the cut list, give every "later" a trigger. A smaller launch gives a cleaner signal and a faster next test.

Carousel

Startups & Product 1 min read

Vague Requests Cost More Than Slow Launches

A common trap: a growth idea lands in the backlog as "add discount codes". No user, no definition of done, no edge cases, no owner. The team guesses, ships late, reworks. A spec with those five parts is the cheapest conversion tactic.

Carousel

Startups & Product 1 min read

The SOP Is the Spec Your Growth Stack Runs On

A common trap: buying a new CRM to fix a messy lead process. The system then routes the mess faster. Write the SOP first, give it one owner, version every change, and only then configure the funnel. Clean process, cleaner data.