"Just because something can be built doesn’t mean it should." We've been hearing this more and more with the rise and ease of AI use in teams. Its a push and pull of speed and impact. What we're breaking down this week is how to slow down and truly assess with your team and stakeholders how you're making decisions that serve your business, not with speed, but with intent.
Steve McCarthy reminds us that just because we can build something doesn’t mean we should. Great products sit where three things meet, what customers need, what’s happening in the market, and what your company does best. When those overlap, you build something people truly care about.
DEEP CUT: When possibility drives decisions instead of real demand, teams burn resources without creating real value.
Hsin-Jou Lin explains how the Kano Model helps teams decide what to build when they can’t build everything. Some features are basic and must exist, some make users happier the more you improve them, and some simply don’t matter. By testing an image search MVP with real users, she was able to see clearly what to prioritize and what to cut.
DEEP CUT: When you focus on how a feature makes users feel, decisions get clearer and roadmaps get lighter.
Ryan Ford shares that AI is great at creating templates and rough drafts, but it doesn’t replace real thinking. Tools might get you most of the way there, but the final stretch takes judgment, correction, and strategy. Design leaders should invest more in problem-solving skills and less in just producing polished artifacts.
DEEP CUT: Speed feels productive, but only thoughtful work creates real value.
