Innovation Sprint Planning

One of the best-kept secrets in design strategy? Timing. Big bets don’t happen in a vacuum. They happen on a schedule and most designers miss it. If your November design sprint didn’t land, it probably wasn’t the idea. It was the timing. Planning cycles are predictable, so here’s what I coach designers and PMs to do: 🔁 Start your design explorations three months before planning begins. For most companies, that’s right now August. 🤝 Truly understand your customers and connect with your peers. Learn their goals, dream ideas, and pain points. Find the threads. Start tying them together. 🧭 Define the kind of sprint your team needs. Build the narrative. Sketch the prototype. Do it before the storm hits. 🎤 Practice your pitch at least 10 times. Share it. Test it. Shape it. By the time the high-stakes meetings roll in, you’ll already know the questions and you’ll have the answers. Bonus: this also builds organizational momentum. ⸻ May and November sprints? Too late. 🎭 Those are theater. You’re not making impact. You’re putting on a show. 📆 You should be shaping ideas months before the planning schedule gets announced. 🚫 You’ll encounter resistance to planning this early, but those folks aren’t thinking strategically. The experienced ones will get it. ⸻ Want to be taken seriously? 🎯 Pick one business metric: growth, retention, or revenue. Maybe a wildcard if there's something truly unique for the company. 👋 Don’t hand-wave at vague “opportunity.” That’s code for “I don’t know how this helps the company.” 📌 Be targeted. Be specific. ✨ Magic wands don’t get funded. Strategic bets do. ⸻ Inside track: 💰 H1 is for bold moves (start in august). That’s when the big money gets thrown around. 📈 H2 is for hitting your numbers (start in March). Partner with ops. Learn which metrics need support and design accordingly. Help earn that bonus check. 🗣️ Don’t wait for the design to be done. Start selling the idea now. Share it. Test it. Shape it. Let feedback sharpen both the strategy and the solution. This is how you hone your storytelling skills. 🗓️ This doesn’t apply to every company. Some don’t plan by halves; they may plan around key moments, like back-to-school or tax season. Understand your company’s investment rhythms. Make that your first discovery when you join a new place. ⸻ Successful design isn’t just what you create. It’s also when you show up. ⸻ To all the designers who I've led in the past, here's the Monday morning announcement: It's planning season. Start figuring out the big dreams for 2026. Let's get those ideas on the roadmap!

The standard two-week sprint cadence just simply doesn’t work for an early-stage startup... As a founder of a company at the earliest stages, there’s a nearly infinite number of things you could be doing that might move your business forward. They say you should always be tackling “the biggest risk to the business” – I’ve come to understand that figuring out what that is ends up being more than half the battle. Recently, the Ditto team has developed a new way to operate that gives us space to develop a perspective and make big bets with confidence. The catch? It involves NOT writing code for weeks at a time… Since launching Ditto, we’ve doubled our user base twice in the past two months. As the firehose of feature requests, bug fixes, and new ideas comes in, it’s become more and more difficult to zoom out and do higher level thinking. It’s easy to justify fixing one more bug or shipping that small piece of polish that so many users are asking for. But we were seeing all of that busy work trade off with our ability to zoom out and take a third-person perspective of where we were heading. From this, we’ve learned two important lessons: 1. It’s important for us to intentionally create space to think, reflect, and explore. 2. We can take data into consideration and from our own opinions. But, at the end of the day, we always follow our instincts. Taking inspiration from Basecamp's (37signals) Shape Up, we decided to split our sprints into two separate phases. Phase A: For two weeks, we focus on discovery, research, analyzing data, talking to users, and forming opinions. During this period, we are having hours of conversations, spending time writing memos, and formulating bets. During this time, we also don’t write a single line of code. Phase B: Then, for the next four weeks, we’re focused entirely on building without looking at any metrics or doing any planning outside of the work we committed to shipping. When I explain this process to other technology leaders, they think we're either brilliant or completely unhinged. This approach doesn’t feel natural. The easiest thing to do as a founder is to just maintain the path in front of you. Especially for social apps — you’re constantly receiving validation from a small cohort of users who request new features and pull you in different directions. Startups at the earliest stage are walking around in a maze in the dark. Without being able to zoom out and assess what’s happening at a higher level, that path can kill your company unless you’re very, very lucky.

Most innovation dies after the whiteboard. Not because the idea was bad, But because the execution loop was broken. Most teams stop at brainstorming. But real innovation compounds when you operationalize it. Here’s the 8-step loop that turns innovation into operating muscle 👇 The Innovation Loop: From Idea to Scaled Impact 1. Set Bold & Outcome-Driven Goals ↳ Anchor to business outcomes ↳ Avoid vague ambition 2. Enable Cross-Functional Collaboration ↳ Break silos early ↳ Involve builders, not just planners 3. Fuse Diverse Ideas into a Clear Concept ↳ Combine, don’t collect ↳ Clarity beats creativity 4. Stress-Test for Strategic Value ↳ Will it scale? ↳ Does it solve a core problem? 5. Prototype at Speed, Not Perfection ↳ Launch small, learn fast ↳ Progress > polish 6. Execute with Accountability ↳ Assign clear owners ↳ Track with real metrics 7. Review with Brutal Clarity ↳ Kill what’s not working ↳ Double down on traction 8. Institutionalize & Scale or Pivot ↳ Systematize the win ↳ Or reboot smarter Innovation isn’t a phase. It’s a loop. And most teams don’t finish the first one. Which step is slowing your loop? ♻️ Repost to help more teams turn innovation into execution. 🔔 Follow Nadir Ali for strategy, leadership & productivity insights.

As CIO I’ve seen months building time and millions in budget wasted on ideas never reaching prod. There were many things not working as they could, but if I had to change ONE thing, it would be this one: When evaluating use cases the process was something like 1 - brainstorm use cases 2 - put them into Excel 3 - Discuss “potential value” 4 - Pick on value + gut feel 5 - Measure delivery, not impact Leading to many dead ideas and wasted budget, because the use case was too complex, too big, it took too long to develop…. There are MANY things worth improving in the way enterprises realize use cases. But if I could go back in time and only change ONE thing, it would be the core methodology. Here's the framework we use at Calibo today, to evaluate opportunities: Phase 1: Use Case Discovery  → Start with business problems, not AI capabilities → Define measurable KPIs upfront (revenue impact, cost reduction, time saved) → Check if someone already solved this (avoid reinventing the wheel) Phase 2: Strategic Scoring  → Rate each use case on Impact, Feasibility, and Strategic Fit → Size the effort (Small = 4 weeks, Medium = 8 weeks, Large = 12+ weeks) → Kill bad ideas early, double down on winners Phase 3: Rapid Prototyping  → Build in 8-10 week sprints maximum → Test with real users and real data → Measure actual performance vs. projected KPIs Phase 4: Business Validation  → Track results for 90 days post-deployment → Document what worked, what didn't, and why → Scale winners, sunset failures This methodology helps enterprises avoid the POC graveyard that I saw fill up as CIO. We've documented this in our full Digital Business Innovation methodology. But even these four phases would transform how most organizations approach AI. Repost this to your network if this was helpful! P.S. If you want our full 66 page innovation methodology document, there is a link in the comments.