Watch where the time goes on your next project.
The design itself may take days. The waiting takes weeks: for feedback, for a decision, for the right person to join a meeting, for someone to confirm what changed. Then a deadline arrives, and everyone says design is the bottleneck.
No process diagram fixes that. Nor does a better project tool. What helps is making decisions visible.
Process is not paperwork
Designers often hear the word process and picture templates and approval gates. I understand why. Bad process protects people from blame. Good process protects time for thinking.
Here is my test: if removing a step would not increase risk, the step should go.
The four questions every project must answer
- What decision are we making now? Not the whole project. This week's decision.
- Who decides? Many people can advise. One person must be able to say yes.
- By when? A decision without a date quietly becomes a delay.
- What happens if we get it wrong? Reversible choices can move quickly. Costly ones deserve more evidence.
That fourth question is the one I value most. It stops teams from applying the same effort to a label and a platform decision.
A simple rhythm for design projects
| Stage | What happens | Output |
|---|---|---|
| Frame | Align on the goal, metric, users and constraints | One-page brief |
| Understand | Research, data review and competitive benchmarking | Agreed insight and assumptions |
| Explore | Test different directions early | Chosen direction and reasons |
| Build together | Design and engineering work side by side | Tested flows and components |
| Learn | Measure the result after release | Next decision |
The stages can overlap, and they often should. What matters is that everyone can see where the work stands and what is blocked.
Protect the three things that get squeezed
Research time. McKinsey's design study found only about half of surveyed companies did user research before generating first ideas. It also found a strong link between successful companies and those that resisted cutting research, prototyping and concept budgets at the first sign of trouble.
Early prototypes. Almost 60% of companies in the same study used prototypes only for internal production testing late in development. That is an expensive way to find out you were wrong.
Learning after launch. A project does not end at release. If nobody checks the outcome, your next estimate is a guess.
What I bring to a team
I started my career in 1997, and I have seen process work well and badly across large organisations. The best teams I have worked with share one trait. People can tell you what is happening without opening a status report.
I have also built process from nothing. Between 2009 and 2014, I ran my own design agency, Shubh Creatives. I had to set up the recruitment, mentoring, performance and delivery frameworks that let a team of 17 serve more than 300 clients without me checking every file.
That calm is not an accident. Someone built it.
Questions people ask
What is design process management? It is the way a team plans, coordinates and tracks design work so that decisions, owners and risks stay clear.
Does process slow down creativity? Bad process does. Good process removes confusion, so people spend more time on the creative work itself.
Where does your team wait the longest?
Tell me. I am genuinely curious, and it is often the quickest way to find what to fix. You can reach me at pranjal.productmind@gmail.com.