The Fountain Institute is an independent online school that teaches advanced UX & product skills.
The Biggest Hurdle in Strategic Projects
The Biggest Hurdle in Strategic Projectsby Jeff Humble Dear Reader, Strategic projects can fall into a million difficulties, but one hurdle takes down more designers than any other, and the sooner you prepare for it, the better. What is the hurdle? It’s the possibility that your strategic deliverable will be ignored entirely. Why strategic projects fail…🦗We often start strategic projects with too much optimism. After bumbling around for a few months trying to figure out how to align your work with all the existing visions, OKRs, and strategic plans, you might regret calling yourself a "strategic" designer. To complicate matters, you want the whole team to adopt your plan, which is challenging even for something as small as a team-level strategy. For example, a UX strategy is easily ignored if not done well. The biggest hurdle in strategic projects is the last hurdle...the one where people start adopting your strategic deliverable. After months of work, all you get is crickets 🦗🦗🦗 What can you do? Bring your decision-makers and teammates into the strategy process! If it's a big project, they’re probably creeping on your work already.
You might as well let them in. Here are three specific tips that will help you do that: 1.) Build a coalition for the project.Start the project by building a coalition of people who care about the outcome and share the work. When people participate in a project, they’re usually more invested in the outcome. 2.) Stay a few steps ahead of the team.Even if you’re taking a collaborative approach, that doesn’t mean you must go the same speed as everyone else. Your focus should be on designing the project plan, and it helps to know what the project process looks like. Use my Strategy Canvas if this is your first strategic project. 3.) Frame the problem together.One of the biggest reasons people ignore your strategy is that they don’t "feel" the problem. Prioritize the research before the solution...just like in regular projects. Once everyone involved agrees on the problem's diagnosis, you can move on to the treatment, a.k.a. your strategic solution. Those tips should help you avoid those crickets. For more guidance, check out my strategy course if you want to improve your strategic skills.
Together, we go through the process, and I provide feedback every step of the way. It’s one of the best ways to gain experience designing strategies before you do it for real. Learn more about the course here. (This article originally appeared in Jeff's blog) Source
Until next time, y'all! ✌️
P.S. If you have feedback on this newsletter, hit reply and drop me a line! |
The Fountain Institute
The Fountain Institute is an independent online school that teaches advanced UX & product skills.
Title of Newsletter in Titlecase By Hannah Baker Dear Reader, Before we jump into new ideas for the year ahead, we wanted to pause for a moment. If your inbox was anything like ours last year, there’s a good chance you missed a few newsletters. So instead of sending another new idea right away, we put together a curated catch-up, a handful of pieces from 2025 that capture the questions we kept returning to. If you only read a few things from us last year, these are a good place to start. 🧠...
What Can't AI Do in Design in 2026 By Hannah Baker Dear Reader, If you work in design, your feeds are probably saying the same two things on repeat: Here’s everything AI can do for you, and Here’s why you should be terrified. Most of that conversation focuses on tools and job titles: “Will designers be replaced?” “Which roles are safe?” It makes for good headlines, but it’s not how the work actually changes in real life. A few months ago, walking to my studio listening to a Planet Money...
Does the Double Diamond make sense for AI-enabled teams? by Jeff Humble Dear Reader, For twenty years, the Double Diamond has been our north star. Discover, Define, Develop, Deliver. It's elegant. It's teachable. It's in every junior's UX case study. And it made sense…when it was created. All that upfront research made economic sense when coding was the most expensive part of the process. Better to get it right before handoff because it's expensive for engineering to make changes later. But...