Agile Isn’t Magic: It’s Listening
Post 1: Agile Doesn’t Mean Psychic: Involving Users from the Start
A Three-Part Series on Making Agile Development Actually Work
An update/rant from Storm King.
Introduction to the Series:
Agile development promises speed, flexibility, and user-centric design. But let’s be honest — many organizations claim to be agile while operating like stubborn hierarchies. They’re sprinting but in the wrong direction. Why? Because they’re locked in their own bubble, assuming they know what users need without ever asking them.
As Steve Blank famously said, “There are no answers in the building.” Yet, countless MVPs are built from the top down, with leadership’s vision mistaken for user needs. We’re currently supporting a client facing this very challenge: balancing leadership’s goals with real user requirements.
This series explores the hard truth about agile development: If you’re not talking to your users, you’re just talking to yourself. From identifying real users and using Design Thinking to validate assumptions, to making sure the requirements we build toward actually serve real needs — this is about getting it right.
In this first post, we highlight how organizations often treat agile development like a mystical art where solutions magically appear without engaging real users. But if you’re only testing internally, you’re just playing a high-speed guessing game.
Agile Doesn’t Mean Psychic: Involving Users from the Start
In the world of agile development, there’s a critical truth: building something useful requires involving users early and often. Yet, many organizations fall into the trap of building Minimum Viable Products (MVPs) based on leadership’s assumptions rather than direct user needs. While the agile methodology is supposed to be user-centric, the reality often looks more like a top-down guessing game.
We’re currently supporting a client where this flawed approach is in full effect. Our goal is to protect our client’s interests by ensuring requirements meet their needs and actually create efficiencies at the operational level. It’s a delicate balance between keeping the process moving forward and making sure the end product doesn’t just work — but works for them.
And here’s where the famous Steve Blank quote rings true: “There are no answers in the building.” You can brainstorm, hypothesize, and whiteboard your way to exhaustion, but if you’re not actively engaging with real users, you’re just guessing. True user-driven development only happens when you step outside your comfort zone and listen.
The Agile Development Process: How to Do It Right
1. Discovery Phase: Getting It Right Before You Build
Before building the MVP, developers should engage users directly through interviews, surveys, and observations. The goal is to gather insights about pain points, desired outcomes, and what “better” actually looks like from a user’s perspective. This phase should be about understanding the problem, not just checking off requirements handed down from above.
2. Prototyping & Concept Validation: Testing the Idea, Not Just the Tech
Prototypes — wireframes, mockups, or low-fidelity designs — often reveal glaring issues. Sharing these concepts with users early on provides invaluable feedback before investing time and resources into building a functional MVP.
3. MVP Development: Building With, Not Just For, Users
During the build phase, continuous feedback loops are critical. This can involve user advisory panels, usability testing, or even just showing rough, incremental builds and actively listening to what users say. Rapid prototyping helps keep users at the center of the development process.
4. Testing & Iteration: The True Power of Agile
Once the MVP is launched, real-world feedback becomes the guiding light. Metrics, interviews, and A/B testing show what’s working and what’s not. The trick is to keep users engaged in prioritizing features and refining workflows — something only possible when they’ve been involved from the start.
The Mistake Many Organizations Make
The biggest mistake organizations make is treating the MVP as a finish line instead of a starting point for meaningful, user-driven iteration. And while leadership’s vision is important, it should be tempered by real-world user input, not just assumptions about what users want.
Our work with our client is focused on ensuring the solution meets their actual needs and creates efficiencies that matter where it counts most. That requires constant engagement, feedback, and a willingness to adjust course when users point out gaps or inefficiencies.
At Storm King, we understand that true agile development isn’t about delivering products quickly — it’s about delivering the right products. We work closely with our clients to bridge the gap between leadership’s vision and real user needs. If you’re tired of top-down solutions that miss the mark, let’s talk. We’ll help you get out of the building, engage your real users, and build something that actually works.