Agile Design Methods
  • Blog
  • Methods
  • Resources
    • Online Course
    • Mobile App
    • Public Course
  • Contact Chuck
  • Search

Agile Design Methods: Design the What

3/29/2018

1 Comment

 
Design work is enabled by conversation with various stakeholders. Agile design methods focus on discussing and describing WHAT is to be produced before describing HOW it is to be developed. 

Here is a quick primer on agile design methods, where they fit in solution development lifecycle and how they differ from agile development methods like Scrum.
The big takeaways:
  • Design requires a conversation with stakeholders
  • Agile design methods engage owner/user stakeholders to design the WHAT
  • Agile development methods engage delivery stakeholders to design the HOW

Resources:
  • Agile Design Methods: A Conversational Approach - In-depth blog post

Picture
1 Comment

Introductions: Capturing Critical Context in the First Few Minutes

9/29/2017

0 Comments

 
Picture
”Tell us a little about yourself and what your organization does in the overall process.”
It passes so quickly that you’ll miss the opportunity if you’re not paying attention.

It’s that initial moment in the process when a person introduces themselves, shares who they are and what and their organization does.

That moment is rich with potential and it goes by quickly.

What To Listen For

Be prepared for the moment in advance by having your co-facilitor serve as a scribe, recording the person’s name on a single sheet of paper or in a note-taking tool like Evernote.

Then your scribe should listen for and record any of the following items that the person mentions:

​Nouns
  • Their name
  • Their organizational role name
  • Workproducts (things they or their organization produce or services they deliver)
  • Collaborators (people they work with or interact with to get things done or do things for)
  • Systems or applications they use to help them
  • Things they respond to

Verbs
  • What they do or produce
  • ​When they do it
  • Triggering business events that they respond to

Pain Points / Opportunities
  • ​Problems they describe​

Example

“I’m Juanita and I work for the Finance Department. We use Dynamics to produce final paychecks when an employee departs and work with Legal and Procurement and Travel to ensure that any garnishments are taken out prior to their final paycheck and that any reimbursements for travel expenses are also included in their last paycheck. We also produce W-2s for departed employees at the end of the year. It’s a challenge and a very manual process to get all of this done thoroughly in a short timeframe, particularly when an employee departure occurs quickly.”

Nouns
  • ​Juanita
  • Finance Department
  • Final paycheck
  • Expense reports (travel expenses)
  • Reimbursements
  • Garnishments
  • W-2
  • Legal Department
  • Procurement Department
  • Travel Department
  • Dynamics application

Verbs
  • When employee departs: Produce final paycheck
  • At year-end: Produce W-2 for employee

Pain Points / Opportunities
  • ​Getting the final paycheck done thoroughly in a short timeframe is a highly manual process.​

What To Do With This

Hold on to them. They will come in handy in the structured conversation that will unfold in the hours and days that lie ahead.

Nearly every one of these nouns are added to a Glossary. Many of them will eventually be placed around a Circle of Interaction (COIN) diagram that clearly summarizes the process, collaborators and deliverables on a single page.

Why This Matters

When it comes to facilitating and producing a clear understanding of a domain under discussion, if it hasn’t been written then it hasn’t been said. To say it another way, if it’s been said, but hasn’t been recorded, then it will not have the potential to be added to design documentation.
Anticipating this rich time of sharing that naturally occurs at the onset of a structured conversation helps you to seize the moment as a facilitator.
When it comes to facilitating and producing a clear understanding of a domain under discussion, if it hasn’t been written then it hasn’t been said.
Being intentional to listen for and record things that a stakeholder mentions serves the stakeholder and the conversational process well. It keeps things agile. It serves the stakeholder well by respecting their contribution to the conversation. It serves the process by maintaining velocity, by creating a corporate memory of what was mentioned and by listening for those things which will be part of the future-state design documentation.

Want More?

Subscribe to my free blog updates to receive content that vividly describes the techniques and leadership skills that embody the practice of agile design methods. The blog contains not only my ideas on the topic, but the insight of others who actively work and thrive wholeheartedly in the realms of collaborative creativity.

Join us.
0 Comments

Agile Design Notions

9/1/2017

2 Comments

 
Agile design methods make process design conversations flow with better collaboration and results.

Making this happen requires intentionality. Here are some notions that influence how to lead and facilitate a group of people using agile design methods.
  • Design "What" before designing "How".
  • Describe "What" using only domain terminology not solution terminology.
  • Defer designing the "How" to solution designers and architects.*
  • Never call a meeting without defining an objective and deliverables.
  • Leave your organizational hat at the door in design meetings.
  • Make design meetings collaborative, kinesthetic, non-digital and visual.
  • We make progress as we write things down. 
  • An idea not captured is an idea lost.
  • Having multiple whiteboards in a meeting room enhances flow.
  • Your smartphone camera is your friend for capturing whiteboard work and moving forward.
  • When the hive stops buzzing, it is time to take a break.****
  • Trust is an accelerator. Fear is an inhibitor.
  • Trust modeled by leaders begets trust in the meeting room.
  • A conversational framework is more important to have during design meetings than a having solution framework.
  • It takes less time to be approximately right than it does to be precisely wrong.
  • Friends develop solutions. Enemies only deliver documentation.*
  • "Tell me more" is a magic phrase that leads to the discovery of real issues/problems.*
  • A market problem always has a significant emotional component to address.*
  • Never ask a question with the answer in mind.
  • As a facilitator, stating what you see is as effective as asking a question of the group.
  • "I don't know" is a safe first response that ultimately must be assigned and answered.
  • Always have a scribe working in the room.
  • People routinely fail at following a process. However almost anyone can immediately perceive when something is out of alignment.**
  • Confusion is costly.***
  • Clarity puts a stop to confusion.

* Pragmatic Marketing
** Paraphrase inspired by Alistair Cockburn
*** Jeff Jones of Bild
**** Gary Evans of Evanetics
2 Comments

Agile Design Methods: A Conversational Approach

8/18/2017

0 Comments

 
Picture
Agile design methods are powerfully simple techniques and leadership skills that make process design conversations flow with better collaboration and results.
​

The resulting design is typically produced at a lower cost than traditional methods with a high degree of precision and improved stakeholder engagement and satisfaction.

When considering how to get from understanding a problem to designing and delivering a solution, the process is a predictable set of conversations that inform every step along the way from ideation to delivery.

​Getting "from-concept-to-market" faster and more effectively yields competitive advantage as well as a solution more likely to resonate with the people who will ultimately buy or use it.

The concepts described herein apply whether your field of endeavor is operational excellence or product development.

As an organizational leader facilitating efforts to improve a process or product manager engaging your design team, you face predictable challenges when moving from some vague notion of a concept to actually designing the solution.

Here are some aspects that affect your future state design process:

  • Clarity
    Why are we doing this?
    ​Why does it matter?
    What problems are we trying to solve for and who will buy/use our solution?
    How do the problems materialize in the quality of life of those affected?
    How else does the problem materialize?
    What are the qualities of the ideal solution?
​
  • Velocity
    How do we get the design flywheel started?
    What does progress look like in the early stages of the process?
    How do we create a "fast path" to produce high-quality design deliverables that will inform the designers and architects of the envisioned solution?

  • Engagement
    How do we develop trust and confidence within the design team?
    How do we acquire the whole-hearted participation of the people tasked with designing the solution?
    How do we vet the impact of the envisioned solution with potential buyers/users?

A Solution-Oriented Conversational Framework

So just how does one get from concept to delivery? 

The process for getting there is easily represented as a series of conversations.
"We've got a long way to go and a short time to get there." 

- Jerry Reed
​Early conversations focus on Why and What: 
  • Understanding what the problem is and why it matters, and designing by describing what the ideal qualities of the solution entail, in just enough essential detail.
  • These conversations are enabled via agile design methods that produce specific deliverables intended for decision-makers, stakeholders as well as solutions designers and architects.

Latter conversations focus on How:
  • Designing and delivering the solution.
  • These conversations are enabled by agile development methods that produce specific deliverables intended for decision-makers as well as solutions developers and delivery channel stakeholders.

This approach lends itself to introducing the right conversation at the right time.
Conversation #1: Learning and Discovery

The scope of this conversation pertains to the understanding of the problem. ​This conversation is in scope of agile design methods.​

Allow the voice of the people who are experiencing the problem(s) to inform this conversation. Listen and learn and document that learning to describe what each problem looks like and summarize them in problem statements in addition to statements of what is working well.

Document this learning and discovery conversation to inform the future state design conversation. Decide whether or not to proceed to a future state design conversation.

Conversation #2: Future State Design

The scope of this conversation pertains to the describing the ideal solution. This conversation is in scope of agile design methods.

Allow a dedicated and accountable group of contributors to inform a conversation around describing "what" the ideal solution looks without describing "how" the solution will be implemented. The descriptive language is free from any implementation jargon and focuses on delivering a clear description of the envisioned solution that may include process definitions, key solution deliverables, user experience criteria, risks, issues and opportunities.

Document this future state design conversation to inform the solution development conversation. Decide whether or not to continue to a solution development conversation.

Conversation #3: Solution Development

The scope of this conversation pertains to designing and developing the solution. This conversation is out of scope of agile design methods. 

Allow a dedicated and accountable group of designers and architects to inform a conversation that describes "how" the ideal solution will be implemented. The descriptive language is rich in implementation detail. It may provide design alternatives that provide varying degrees of cost, risk, time, return on investment, etc. Decisions are made regarding design alternatives and leading to the actual development of a solution.

Document this solutions development to inform the solution delivery conversation. This conversation is out of scope of agile design methods.

Conversation #4: Solution Delivery

The scope of this conversation pertains to the delivery and support of the solution. This conversation is out of scope of agile design methods.

Allow a dedicated and accountable group to inform a conversation that oversees the delivery of the solution. This includes launching and promoting the solution as well as supporting it and providing user experience feedback to inform solution improvement efforts.

Agile Design Methods Describe What Not How

Agile design methods are those techniques and leadership skills that enable a future state design process characterized by high velocity, collaborative engagement and clarity of ideation. The resulting design is typically produced at a lower cost than traditional methods with a high degree of precision and improved stakeholder engagement and satisfaction.

The outputs of these conversations intentionally stop short of designing the implementation, They describe what the problems are and what the ideal solution qualities look like. This informs solutions architects and designers who are responsible for determining how to design the solution and the production/development teams that will deliver it.
Picture
Agile Design Methods: The What Perspective
Agile design methods, as quickly as practically possible, describe what is envisioned to be an ideal process or solution. They produce ideation deliverables that describe what the problems are and what the ideal solution qualities look like.

Exercising this type of "Design the What" discipline respects a separation of concerns between the market problem definition and the solution design definition. It informs the solution designers and architects who are responsible to "Design the How" of the solution under discussion.

​At the time of this writing, the phrase "agile design methods" is not widely used or understood.
Agile Development Methods: The How Perspective
In contrast, agile development methods, as quickly as practically possible, define how to architect the solution and then proceed in building and delivering that solution. They ​produce deliverables that describe how the solution is to be implemented and they produce the actual solution. ​

At the time of this writing, the phrase "agile software development" is commonplace and is routinely associated with the word "agile".

Agile Design Methods: Subscribe for "How To"

The purpose of this primer has been to establish a foundation of a conversational framework that provides context as to where agile design methods fit in an overall solution development life cycle.

It sets the stage for further elaboration on topics related to agile design methods, collaborative creativity, product development and user experience.

- Chuck

Subscribe to my free blog updates to receive content that vividly describes the techniques and leadership skills that embody the practice of agile design methods. The blog contains not only my ideas on the topic, but the insight of others who actively work and thrive wholeheartedly in the realms of collaborative creativity.

​I look forward to you joining us. It's going to be quite a journey.
Learn the Secrets of Successful Agile Designers
0 Comments

    Learn the Art of
    ​Successful Agile Design

    Picture

    About Chuck Boudreau

    (boo'-dro) - I help people design solutions collaboratively using agile design methods. I have 30+ years of experience in designing software solutions and business processes, leading cross-functional process improvement teams as a business analyst, and helping product managers define and position products using Pragmatic Marketing. I am passionate about user experience design, dog training, beating drums in musical ensembles and collaboratively creating solutions with people.

    Chuck's Resume
    File Size: 67 kb
    File Type: pdf
    Download File



    Archives

    April 2018
    March 2018
    February 2018
    January 2018
    November 2017
    October 2017
    September 2017
    August 2017
    July 2017
    June 2017
    May 2017

    Categories

    All
    Agile Design
    Boredom
    Collaboration
    Connecteness
    Conversational Framework
    Design Insights
    Design Specification
    Design The "What"
    Documentation
    Empathy
    Environment
    Facilitation
    Feature Lists
    Future State Design
    Glossary
    Ideal Solution Statement
    Leadership
    Learning And Discovery
    Marketing
    Meetings
    Observation
    Pitfalls
    Problem Statement
    Requirements
    Scribe
    Solution Design
    Solution Designers
    Solution Development
    Solution Marketers
    Success Criteria
    Tips And Techniques
    Trust
    Use Cases
    Users
    User Stories
    Velocity

    RSS Feed

© 2016-2022 Chuck Boudreau | Privacy Policy

Photo used under Creative Commons from Sasquatch I
  • Blog
  • Methods
  • Resources
    • Online Course
    • Mobile App
    • Public Course
  • Contact Chuck
  • Search