Estimating design work in hours sets teams up to fail. But story points help designers earn trust, align with product managers, and keep creative space intact. This week, we unpack how adopting story points can shift the way your team plans and communicates. |
What if the secret to better collaboration wasn’t a new tool or process, but a number?
🧑🎨 Designers estimate in hours.
🧑💻 Engineers estimate in points.
🤡 Product managers are left to juggle both.
No wonder everything feels misaligned!
But first, check out this week's sponsor:
SPONSOR
Tired of generic LinkedIn tips and “insider secrets” that aren’t actually secret?
The Jaw Breaker from Amy Santee delivers grounded, candid advice for navigating UX careers in the real world. Because you deserve guidance that’s actually useful. No spin. No sugar-coating.
|
|
We might have a communication problem!
➡️ Designers commit to “10 hours” that never account for iteration.
➡️ Engineers estimate in Fibonacci points that sound like developer math.
➡️ Stakeholders assume both mean the same thing.
Here’s the thing: story points aren’t just for developers.
When designers estimate in story points, they:
⇢ Align with engineering on a shared language of effort
⇢ Set realistic expectations with product managers
⇢ Protect creative time without overpromising
⇢ Earn credibility by planning consistently
This week, I chat with Naresh Shan to unpack why story points are the most underrated tool for UX teams, and how adopting them transforms collaboration.
🎯 Here are some key takeaways from our chat |
1️⃣ Stop equating effort with hours: Estimating design in hours compresses the creative process and sets false expectations. Shifting to effort-based points acknowledges the messy, iterative nature of design while still providing a predictable way to plan.
2️⃣ Use story points to build credibility: When designers speak the same estimation language as engineers, it immediately boosts trust. Story points make it clear you’re not guessing—you’re aligning effort with measurable outcomes.
3️⃣ Create a shared definition of “done”: Story points force teams to break down tasks and agree on what’s included. This prevents scope creep and ensures everyone—designers, PMs, and developers—knows what success looks like.
4️⃣ Plan capacity with confidence: Tracking velocity across sprints gives managers the data they need to balance workloads and push back on unrealistic demands. No more guessing how much your team can handle.
5️⃣ Build trust through consistent planning: Consistency in story point use shows stakeholders that design is reliable. Over time, this builds trust, reduces last-minute requests, and strengthens the working relationship between UX, product, and engineering.
SPONSOR
How often do you stare at a blank Figma canvas, unsure where to start?
Mobbin gives you instant access to over 400,000 beautifully designed UI and user flows from apps you love, and content is added weekly. So you never have to start from scratch again. Quickly find exactly what you need—search by app category, UI patterns, or even specific features.
Ready to level up your design process? Visit mobbin.com/beyondux to get 20% off Mobbin pro today and never run out of inspiration again.
|
|
You iterated, pivoted, circle-backed, and made it out of Q2 (barely).
You’ve earned a Merit-ish Badge!
Choose from three sets:
• Soft Skills, Sharp Tongue
• Cult of Figma Initiation
• Pixel Pusher Survivor Kit
|
|
|
|
|
|
They don't teach this stuff in school
Learn the things they left off the syllabus.
|
Also available at these fine retailers
|
