Sitemaps
How We Secretly Lose Control of Our Startups
Should Kids Follow in Our Founder Footsteps?
The Evolution of Entry Level Workers
Assume Everyone Will Leave in Year One
Stop Listening to Investors
Was Mortgaging My Life Worth it?
What's My Startup Worth in an Acquisition?
When Our Ambition is Our Enemy
Are Startups in a "Silent Recession"?
The 5 Types of Startup Funding
What Is Startup Funding?
Do Founders Deserve Their Profit?
Michelle Glauser on Diversity and Inclusion
The Utter STUPIDITY of "Risking it All"
Committees Are Where Progress Goes to Die
More Money (Really Means) More Problems
Why Most Founders Don't Get Rich
Investors will be Obsolete
Why is a Founder so Hard to Replace?
We Can't Grow by Saying "No"
Do People Really Want Me to Succeed?
Is the Problem the Player or the Coach?
Will Investors Bail Me Out?
The Value of Actually Getting Paid
Why do Founders Suck at Asking for Help?
Wait a Minute before Giving Away Equity
You Only Think You Work Hard
SMALL is the New Big — Embracing Efficiency in the Age of AI
The 9 Best Growth Agencies for Startups
This is BOOTSTRAPPED — 3 Strategies to Build Your Startup Without Funding
Never Share Your Net Worth
A Steady Hand in the Middle of the Storm
Risk it All vs Steady Paycheck
How About a Startup that Just Makes Money?
How to Recruit a Rockstar Advisor
Why Having Zero Experience is a Huge Asset
My Competitor Got Funded — Am I Screwed?
The Hidden Treasure of Failed Startups
If It Makes Money, It Makes Sense
Why do VCs Keep Giving Failed Founders Money?
$10K Per Month isn't Just Revenue — It's Life Support
The Ridiculous Spectrum of Investor Feedback
Startup CEOs Aren't Really CEOs
Series A, B, C, D, and E Funding: How It Works
Best Pitch Decks Ever: The Most Successful Fundraising Pitches You Need to Know
When to Raise Funds
Why Aren't Investors Responding to Me?
Should I Regret Not Raising Capital?
Unemployment Cases — Why I LOOOOOVE To Win Them So Much.
How Much to Pay Yourself
Heat-Seeking Missile: WePay’s Journey to Product-Market Fit — Interview with Rich Aberman, Co-Founder of Wepay
The R&D technique for startups: Rip off & Duplicate
Why Some Startups Win.
Chapter #1: First Steps To Validate Your Business Idea
Product Users, Not Ideas, Will Determine Your Startup’s Fate
Drop Your Free Tier
Your Advisors Are Probably Wrong
Growth Isn't Always Good
How to Shut Down Gracefully
How Does My Startup Get Acquired?
Can Entrepreneurship Be Taught?
How to Pick the Wrong Co-Founder
Staying Small While Going Big
Investors are NOT on Our Side of the Table
Who am I Really Competing Against?
Why Can't Founders Replace Themselves?
Actually, We Have Plenty of Time
Quitting vs Letting Go
How Startups Actually Get Bought
What if I'm Building the Wrong Product?
Are Founders Driven by Fear or Greed?
Why I'm Either Working or Feeling Guilty
Startup Financial Assumptions
Why Every Kid Should be a Startup Founder
We Only Have to be Right Once
If a Startup Sinks, Founders Go Down With it
Founder Success: We Need a Strict Definition of Personal Success
Is Quiet Quitting a Problem at Startup Companies?
Founder Exits are Hard Work and Good Fortune, Not "Good Luck"
Finalizing Startup Projections
All Founders are Beloved In Good Times
Our Startup Culture of Entitlement
The Bullshit Case for Raising Capital
How do We Manage Our Founder Flaws?
What If my plan for retirement is "never retire"?
Startup Failure is just One Chapter in Founder Life
6 Similarities between Startup Founders and Pro Athletes
All Founders Make Bad Decisions — and That's OK
Startup Board Negotiations: How do I tell the board I need a new deal?
Founder Sacrifice — At What Point Have I Gone Too Far?
Youth Entrepreneurship: Can Middle Schoolers be Founders?
Living the Founder Legend Isn't so Fun
Why Do VC Funded Startups Love "Fake Growth?"
How Should I Share My Wealth with Family?
How Many Deaths Can a Startup Survive?
This is Probably Your Last Success
Why Do We Still Have Full-Time Employees?
The Case Against Full Transparency
Should I Feel Guilty for Failing?
Always Take Money off the Table

Process vs. Progress: How to Have Each in Healthy Amounts

Emerson Taymor

Process vs. Progress: How to Have Each in Healthy Amounts

Even dietitians know it’s healthy to have a beer or a donut once in a while. Without wiggle room, a strict diet can harm health in other ways, like creating stress or limiting social interaction.

Until a client prescribed otherwise, our company struggled to take a break from something that was supposed to keep us strong: our process. This client loved our work, but he felt that we’d become too married to our own way of doing things.

A look back at our client data showed that we had, indeed, taken our healthy habits too far. We did our best work when we eliminated VUCA (volatility, uncertainty, complexity and ambiguity), empathized with our clients as well as their users, and pushed toward consistent shipping.

So we broke our mold.

We started incorporating stakeholder personas into the mix, which we use to remind ourselves that the client’s business success matters as much as the user’s ultimate experience.

Today, when we realize that achieving a certain business outcome requires us to go off process, we put our Process Kool-Aid down and do it.

Too Much of a Good Thing

Frustrated looking man at computer

A process is a healthy thing for a business to have. Some startups struggle mightily to find and follow one. But when a process saps a project’s momentum or creates analysis paralysis, it’s time to take a break.

For example, user research is an important part of the process for any company building something for people. But sometimes, designers become so familiar with a problem or project that user interviews become a waste of time.

Other times, it takes a prototype to validate a particular user assumption, so an experiment-driven design may be the best way to move forward. Experiment-driven design’s “hypothesis, ideate, make” cycles champion building over traditional research tactics as the best way to check assumptions.

User research is just one example. Companies can get stuck in their processes in all sorts of ways. On agile teams, for example, scrum masters sometimes forget just how much time those daily checks and meetings can take. Not only are daily meetings unnecessary for truly agile teams, but they can also quickly cut into the team’s sprint schedule.

To be clear, the problem isn’t agile itself; it’s a misunderstanding of the Agile Manifesto’s core principles. Across every version of agile — scrum, SAFe®, Kanban, you name it — those core tenets are what actually drives progress.

Agile promotes adaptability, collaboration, and frequent iteration; it measures progress in terms of software production, not in meetings held or key performance indicators met. Each meeting a team of makers attends pulls its members out of that all-important flow state. Constantly switching back and forth between “work mode” and “meeting mode” can kill their agility and create frustration.

But the answer to an overabundance of process isn’t to eliminate it entirely. Pushing forward without measurements in place or keeping makers out of the loop is unproductive at best and counterproductive at worst.

Instead, think: Which meetings can be killed? Which communications can be handled via email or Slack instead? Can the sprint planning meeting be moved to Monday morning to reduce context switching? Use a light touch. Too many cutbacks at once can create chaos.

When to Pull Back on Progress

When to pull back on progress

Just as important as keeping process in check is preventing runaway progress. To see the problem with unchecked progress, picture a footrace. Unlike most races, this one doesn’t have marked paths or even a finish line. The runners take off, but they don’t know where to go or when to stop. What should have been a straight shot to the finish turns into a mad sprint in every direction.

In the world of business, this dash might look like a team that consistently builds the wrong thing and never seems to hit pay dirt. Because team members didn’t bother to understand why they’re building what they’re building, they waste time creating things that the product’s users won’t want.

If you have tons of work to show but your core metrics are lagging, then it’s probably time to rein in progress. If you don’t, you’ll burn through your capital and wind up with something nobody wants, which doesn’t exactly inspire confidence in investors or clients.

Hitting a little too close to home?

Govern progress with a research-based approach. Start by defining the user’s problem and choosing key metrics carefully.

Then, build prototypes around those user insights. You may not move quite as quickly, but you’ll meet more benchmarks and satisfy more clients.

Not every team has a process or a progress problem, but most could use a better balance.

So eat your greens — in other words, have your processes — but don’t say “no” to that big, hearty helping of progress when you’re hungry for it. Just don’t overdo it.


Also worth a read:

  1. 4 Areas Where You Can Automate Business Processes
  2. Starting a Business? Focus on the Business Process Modeling
  3. Why Companies are Failing to Implement Growth Processes

Find this article helpful?

This is just a small sample! Register to unlock our in-depth courses, hundreds of video courses, and a library of playbooks and articles to grow your startup fast. Let us Let us show you!

Submission confirms agreement to our Terms of Service and Privacy Policy.

Already a member? Login

No comments yet.

Register to join the discussion.

Already a member? Login

Create Free Account