Develpreneur: Become a Better Developer and Entrepreneur How Story-Driven Discovery in Software Projects Leads to Better Results
In this episode of the Building Better Developers Podcast, we sit down with Dusty Gulleson, CEO of eResources, to explore why story-driven discovery is the foundation of every successful software project. Dusty shares how understanding a customer's journey, motivations, and real-world frustrations leads to better outcomes than any technical requirement alone. Instead of focusing on platforms and features first, he explains why great projects begin with people and the stories behind their needs.
About Dusty GullesonDusty Gulleson is a founder who never set out to build a large company—he simply followed the work, served people well, and let loyalty drive the growth. After leaving a COO role that didn't fit, he waited tables, picked up freelance web projects, and gradually built what is now eResources, a 100+ person organization spanning strategy, branding, IT services, cybersecurity, SaaS automation, and offshore teams. Born in Indonesia and now leading four thriving divisions, Dusty has grown the company without hype or outside funding, relying instead on relationships, trust, and consistent delivery. With five acquisitions under his belt and recurring revenue across industries like housing, higher education, and public health, his leadership philosophy centers on people, clarity, and service. Whether in a boardroom or a bourbon tasting room, Dusty approaches every conversation with the same question: "Where do you want to go, and how can we help?"
Why Story-Driven Discovery Matters More Than RequirementsMost clients initially express their needs in bullet points, task lists, or feature requests. But as Dusty explains, those surface-level items rarely reflect the full picture. Story-driven discovery goes deeper by uncovering the context behind the request: the business pressures, the users involved, and the real outcome the client is trying to achieve.
"We're customer service people first — we just happen to do technology," Dusty shared.
This mindset ensures teams build solutions that support real workflows rather than assumptions.
How Story-Driven Discovery Reveals Real ProblemsAs Dusty shifted from a bullet-point mindset to a more narrative-focused approach, he began asking open-ended questions such as:
- What does a successful day look like for you?
- What is frustrating about your current system?
- Which tasks slow you down the most?
- Who depends on the work you do?
Stories expose problems that requirements often hide.
Rob Broadhead offered a relatable example: someone saying "the printer isn't working" may actually mean "I need this document before my meeting." Story-driven discovery uncovers the urgency, not just the symptom.
Using Story-Driven Discovery Before Delivery BeginsDusty breaks every project into two essential steps:
- Discovery — listening, asking questions, and gathering the story
- Delivery — building the solution aligned to that story
Skipping step one is where most projects fail. Without story-driven discovery, teams risk scope creep, mismatched expectations, unrealistic budgets, and frustration on both sides.
"If a company won't invest in discovery, they're not serious about solving the problem."
A proper discovery process creates alignment long before development begins.
Avoiding AI RFP Pitfalls with Story-Driven DiscoveryDusty highlighted a growing issue: AI-generated RFPs that look polished but lack practical context. These documents often include:
- Conflicting requirements
- Unrealistic expectations
- Missing business outcomes
- Undefined user roles
- No connection to real workflows
They list features — but no story.
Story-driven discovery corrects this by grounding requirements in real organizational challenges and goals.
Prioritizing Needs with Story-Driven DiscoveryDuring discovery, Dusty uses two powerful prioritization methods:
MoSCoW Method- Must-Have
- Should-Have
- Could-Have
- Won't-Have (for now)
- 80% → essential for launch
- 15% → valuable future enhancements
- 5% → avoid due to high cost or low ROI
These frameworks help keep projects realistic and focused on value.
How Story-Driven Discovery Builds TrustAt its core, story-driven discovery builds stronger relationships.
Clients feel heard. Developers gain clarity.
Executives stay aligned.
Teams avoid miscommunication.
When everyone understands the story, the success criteria become obvious — and so do the right solutions.
ConclusionThis episode makes one message clear: technology alone doesn't create great software outcomes. Success begins with story-driven discovery — a human-centered approach that uncovers real needs and aligns teams before development ever starts. Dusty's perspective reminds us that the best projects aren't built on specs. They're built on stories.
Stay Connected: Join the Developreneur CommunityWe invite you to join our community and share your coding journey with us. Whether you're a seasoned developer or just starting, there's always room to learn and grow together. Contact us at info@develpreneur.com with your questions, feedback, or suggestions for future episodes. Together, let's continue exploring the exciting world of software development.
Additional Resources