STARTUP
B2B
WEB APP
4 mo
From feature freeze to public launch
+50%
Productive output after cutting circular meetings
1 yr+
Avg. team tenure, up from under 90 days
5 days
New onboarding, down from 2 months
THE SHORT VERSION
A startup stuck in its own loop.
A B2B platform had been in development for 3 years with no launch in sight. Seven siloed teams, zero documentation, and a founder rewriting priorities at midnight. I replaced the chaos with one source of truth, a strict prioritization filter, and real boundaries — then shipped the MVP.
THE CONTEXT
The company was building a cloud workflow tool for independent supplier networks. Angel-funded, ambitious, and certain they'd ship quickly. Six months became one year. One year became three. As the timeline stretched, anxiety scaled with it — and the team kept building an enterprise platform while operating in total daily ambiguity.
WHAT WAS FOUND
Not a tech problem. An operations collapse.
Watching how the team actually worked made the diagnosis obvious within days.
Groundhog Day onboarding
No documentation. New hires figured it out alone, spent two months ramping, and most quit inside 90 days. The cycle never stopped.
THE BLUEPRINT
Three rules. Non-negotiable.
A Foundational Recovery & Launch Blueprint built on three uncompromising pillars.
01
Single Source of Truth
One central workspace. Deadlines, owners, and SOPs visible to all seven departments. Locked.
02
Feature Firewall
No feature ships unless it maps to the original core launch requirements. Data, not gut feel.
03
Communication Boundaries
No more 24/7 Slack. Focused, scheduled review windows protected the team's capacity.
Freeze. Map. Rebuild.
Froze new features. Sat with the founder, mapped the platform's real state, and co-created a bare-bones MVP list.
Built a Change Management gate. Every new idea ran through a validation checklist measuring business value vs. launch delay.
Made roles visible. A transparent directory showed every person's responsibilities across all seven teams.
Rebuilt the design system. A clean, reusable component library let developers ship without constant design loops.
Compressed onboarding. Two-month guesswork became a self-guided five-day sequence with docs and videos. Maximizing volunteer time.
THE OUTOMCE
They finally shipped.
Four months after we froze the feature list, the MVP went public.
EXECUTION
The hardest fix wasn't the workflow. It was the leadership.
There was agreement that the company needed structure — but resisted it the moment enforcement began. Fear of launching anything "imperfect" had the founder bypassing rules and assigning random tasks all at hours.
I countered with empathy, transparency, and one firm tool: a weekly visual Progress Health Report. It tied every structural decision to a real development metric.
When everyone could see, in black and white, that respecting the workflow shipped features — and that mid-week pivots cost the company momentum — acceptance was gained. The team successfully carried the product across the line.
Got a product that won't ship?
The answer is rarely more hours. It's usually fewer decisions, made clearly.
c
2026 SB - Product Design Strategist.