Bringing Clarity, Traceability, and Accountability to Projects with D.R.A.W. – Talk Recap from #LeedsTechTalks

Last week, I had the pleasure of speaking at the latest #LeedsTechTalks meetup hosted alongside Carlene Handley and Christian Newsome. It was a fantastic evening with insight, practical tools, pizza, and great conversations with the local tech community. Thanks to everyone who joined us, especially those who contributed with thoughtful questions and lived experiences. 🙌

My talk? A deep dive into the D.R.A.W. methodology—a way of working that’s been battle-tested on chaotic projects where Agile is claimed but not practiced. It’s not a tool. It’s not a framework you need to “buy into.” It’s a way to bring structure, reduce noise, and drive ownership.

Why D.R.A.W.?

In most projects I join as a QA consultant or Technical Director, the problem isn’t always a lack of tools—it’s a lack of alignment. There are multiple communication channels (Teams, Slack, WhatsApp, Jira, email, etc.) and no single source of truth.

Too often I’ve seen:

• No clear documentation or shared understanding.

• Missing acceptance criteria.

• Businesses do not know what they’ll get until UAT (too late!).

• Silos between devs, testers, and BAs.

• Knowledge is lost when people leave.

So, we created D.R.A.W., a methodology for centralising all key elements in a user story to facilitate collaboration, traceability, and delivery.

What is D.R.A.W.?

It stands for:

• D – Description: What are we solving and why?

• R – Risks: What could go wrong technically or functionally?

• A – Acceptance Criteria: What does ‘done’ look like?

• W – Work Items: Clear steps to get it over the line.

✅ All in one place
✅ Simple to follow
✅ Easy to hand over
✅ Promotes shared accountability
✅ Works in Azure DevOps, Jira, or wherever your backlog lives

D.R.A.W. in Action

I demoed a real-life user story using Azure DevOps, showing how to customise the boards, workflows, and fields to align with D.R.A.W. It’s lean and clean and keeps everyone on the same page—from BA to dev to PM to tester. No micromanagement is needed.

Want a sneak peek? Here’s the structure:

• Description: The context and purpose
• Risks: What could go wrong (data loss, UI confusion, poor notifications)
• Acceptance Criteria: Clear, testable goals
• Work Items: Bullet-style tasks—no waffle, just actions

It’s all visible. All trackable. All in one screen. No more “what’s the latest version of this?” or “was that feedback ever actioned?”

Want Me to Show You How?

I’m working on a training video series that breaks down how to set up D.R.A.W. from scratch—ideal for:

• QA Analysts looking to improve test coverage

• Business Analysts who want traceability and clearer handovers

• Project Managers looking for better governance

• Developers are tired of vague tickets

• Startups or SMEs who wish to be agile without the admin

I’ll walk you through setup in Azure DevOps, share templates, and offer guidance on running this with lean teams or multi-project environments.

Want me to set it up for you?

I offer:

• Do-it-with-you: Collaborate and coach your team hands-on

• Do-it-for-you: We take care of the setup and hand it over

• Remote support or onsite delivery, depending on your needs

Please email or message me on my LinkedIn profile to let me know if you are interested.

Final Thoughts

Thanks again to everyone at #LeedsTechTalks for the great energy. 🙌
Thanks to Carlene Handley (Computer Futures) and Christian Newsome (Digital 575) for the opportunity and support.

This is the start of something that can genuinely change how we work, especially in environments where chaos, miscommunication, and missed expectations have become the norm.

If you want clarity, traceability, and project accountability, join me.