Some problems don’t get solved because they’re too complex, they don’t get solved because we overthink them.
We research. We compare. We model scenarios. We wait for perfect clarity. And in the meantime? Nothing moves.
If your organization has ever stalled on a big decision, design thinking might be the reset button you didn’t know you needed.
The Basics of Design Thinking
At its core, design thinking is a structured way to solve problems by focusing first on people, then rapidly testing ideas (instead of debating them endlessly).
Rather than asking, “What’s the perfect solution?” design thinking asks:
- What problem are we actually trying to solve?
- Who is experiencing it?
- What small change could improve it right now?
It’s not reckless decision-making. It’s intentional experimentation.
Why It Leads to Faster Decisions
Traditional decision-making often looks like this:
Gather requirements → Analyze options → Debate trade-offs → Revisit assumptions → Repeat.
Design thinking flips the script. Instead of building a theoretical solution in a conference room, you test a small, practical version in the real world. You gather feedback. You adjust. You move forward. By embracing experimentation, momentum replaces paralysis.
When leaders see something working (even imperfectly), conversations change. The focus shifts from “What if?” to “What did we learn?”
💫Remember: A 50% solution in motion teaches more than a 100% solution on a whiteboard.
The Five Practical Stages Made Simple
Design thinking is often described in five stages. In business terms, here’s what that really means:
Empathize: Talk to the people doing the work. Not just leadership, actual users.
Define: Clearly articulate the real problem (not the assumed one).
Ideate: Brainstorm possible approaches without over-filtering.
Prototype: Build a lightweight version of a solution.
Test: Put it in front of users and learn from the results.
The magic isn’t in doing these once. It’s in cycling through them quickly. Each loop reduces risk and builds clarity.
Why Organizations Get Stuck
Most stalled initiatives don’t fail because teams lack intelligence, funding, or talent. They stall because the environment doesn’t support forward motion. Here are the most common design thinking blockers and how to clear them.1. Fear of Getting It Wrong
Fear is often the quiet decision-maker in the room. Fear of choosing the wrong platform. Fear of wasting money. Fear of visible failure. Fear of being the one who championed a solution that didn’t pan out. When fear drives the conversation, teams default to analysis, comparison, and delay. It feels safer to keep evaluating than to commit.How to shift it:
Redefine failure as feedback. Design thinking works because it lowers the stakes. Instead of betting everything on one massive decision, you run small experiments. A prototype that doesn’t work isn’t a disaster; it’s data.2. Prioritizing Debate Over Testing
Some organizations mistake discussion for progress. Meetings multiply. Slide decks grow. Spreadsheets compare every conceivable option. But clarity isn’t produced by conversation alone. When debate becomes the primary mode of problem-solving, things stay theoretical. No one sees how an idea actually performs in the real world.How to shift it:
Adopt a “test before we debate further” rule. If two solutions seem viable, build lightweight versions of both and observe user behavior. Real interaction will answer questions that hours of discussion cannot.💡Pro Tip: If you’ve discussed the same decision three times without new information, it’s time to prototype.
3. Psychological Insecurity
If team members feel unsafe challenging assumptions or offering imperfect ideas, innovation stalls, people stay quiet, and risk-taking disappears. Meetings become echo chambers.
Design thinking depends on diverse input. Without psychological safety, ideation becomes narrow and cautious.
How to shift it:
Leaders must model vulnerability. Admit uncertainty. Invite dissent. Reward thoughtful challenges instead of punishing them. When people see that questioning the status quo isn’t penalized but welcomed, better ideas surface faster.
Design thinking thrives in environments where curiosity outweighs ego.
4. Leadership Not Sponsoring Iteration
Iteration requires visible support. If leadership expects fully polished, fully vetted solutions before anything moves forward, teams will hesitate to experiment.
Without executive sponsorship, prototypes feel risky and unofficial.
How to shift it:
Leaders should explicitly endorse experimentation. Set the expectation that early versions are meant to evolve. Allocate time and resources for testing, not just planning.
When iteration is positioned as strategy, teams move with more confidence.
5. Refusal to Revisit Decisions
Some organizations treat past decisions as permanent, even when new information suggests refinement is needed. Pride, sunk costs, or internal politics make it difficult to pivot.
Design thinking, however, assumes that refinement isn’t a weakness—it’s progress.
How to shift it:
Normalize revisiting decisions as a part of growth. Frame adjustments as learning, not backtracking. Create regular checkpoints where solutions are evaluated against real outcomes, not just original intentions.
Flexibility isn’t instability. It’s responsiveness
Momentum Beats Procrastination
The longer organizations wait to address transitions, the more compressed their timeline becomes, and delayed decisions rarely get easier. Design thinking allows you to move forward without overcommitting. It turns a massive transformation into a series of manageable steps. Each small win builds confidence. Each iteration reduces uncertainty. Each test clarifies your roadmap.
Before you know it, you’re not “considering options” anymore, you’re actively evolving.
Remember, progress creates clarity, while clarity rarely comes before progress.
The Bottom Line
Design thinking isn’t just for product designers or innovation teams; it’s a practical framework for breaking decision paralysis.
When you focus on the impacted people, test small ideas, and iterate quickly, decisions become less intimidating and more actionable.
And if you’re dragging your feet on a major shift (cough, cough, moving off Project Online), design thinking might be exactly what turns hesitation into forward motion.
Sometimes the fastest way to decide…is to start.
Reach out if you’d like help learning your options, prototyping a solution, or testing out potential new software. We’re here to help!
Applying Design Thinking to the Project Online Transition
Let’s sidebar to talk about the elephant in the room.
Despite its fast-approaching retirement, many organizations are still using Project Online. Not because it’s perfect, but because transitioning feels overwhelming.
The questions are familiar:
- What’s the “right” replacement?
- How complex will migration be?
- Will we lose functionality?
- What if users don’t adopt the new system?
Those are valid concerns. But waiting for absolute certainty isn’t a strategy. It’s a delay tactic.
This is where design thinking becomes powerful.
Instead of Debating the Perfect Platform…
Start with one department, one project.
Choose a potential solution. Maybe it’s a modern Microsoft solution (Planner Premium with Project Accelerator or Project Operations), maybe a 3rd party Power App, or maybe it’s not in the Microsoft ecosystem at all.
What matters is that you test it. Configure it lightly, but don’t over-engineer it. Let real users interact with it and then gather feedback. Ask, “What worked? What didn’t? What needs refinement?”
Suddenly, you’re not theorizing about the future. You’re learning from real usage.
💡Pro Tip: A designer doesn’t need the whole picture figured out to begin work, and you don’t need a full migration plan to begin. Transitioning begins simply, with one controlled experiment.
