Advice Process for Effective Organizational Decision-Making
The goal of Enterprise Agility is to have a nimble, flexible organization. To reach this end we need to have a clear decision-making process that supports autonomy and learning while achieving effective outcomes.
The Advice Process is easy to understand. Anyone in the organization can make a decision provided they get advice from everyone who will be meaningfully affected and people with expertise in the matter. The Advice Process helps organizations develop trust, ownership and learning to create a nimble organization. The Advice Process originates from corporate innovation as documented in “Joy at Work” and “Reinventing Organizations”
In this hands-on session you will learn how to use “Advice Poker” cards as a sense-making and education tool to explore how decisions are made and can be made. The Advice Process will be contrasted with other approaches such as consensus and traditional hierarchical decision-making. You will walk away with a powerful tool to invite greater levels of trust and ownership to allow Agile to scale.
Outline/structure of the Session
The topic of decision-making has been addressed in our community through excellent efforts in this area such as Delegation Poker, Decider Protocol, Lean A3 Technique. The Advice Process takes decision-making to the next level to help us more effectively support Agile not just at a team level, but across the whole organization.
The session will be delivered as an experiential workshop. This is how I intend to structure the time.
* Welcome/Objectives [3 min]
* Warm-up exercise: How are decisions made in your org? How much autonomy is there? Is there space for risk and learning? Reflect and share at your table. Large group sharing on experience (Build histogram of responses). [7 min]
* Advice Process Intro – definition and use – give people a one page handout to solo-read. Discuss at tables what would happen if this was followed (good, bad, interesting). Large group debrief. 
* Advice Poker Cards 
* Solo exercise: write down 5 decision you made (or were involved with) in the last week and 5 decisions that you need to make (or be involved with).
* Introduce and explain cards.
* Solo exercise to use cards to clarify involvement. What was and what ought to be.
* Table discussion followed by large group share + Q&A.
* Using Advice Poker to Create Ownership Agreements. Solo work to identify areas of unclear ownership (at work) that are causing challenges and the parties involved. Group to pick some examples and discuss what card each group may play. Discussion and large group sharing. Presenter to share some remarks on using this to surface tensions. [15 min]
* Create your action plan. 2 min solo & then 3 min table sharing [5 min]
* Questions & Answers [5 min]
I have been using the advice process with my clients as part of normal work as well as within the Toronto Agile Community not-for-profit. I have created a custom set of cards that are used to teach the advice process and used in real life to clarify decision-making. I have been training clients on this method, however, this workshop will be a novel creation that takes a broader look at decision-making in the enterprise.
This session was run at Agile 2106 in the Enterprise Agility track. I intend to shorten it to meet 60 minute timeframe.
- Able to use advice process in daily interactions with others
- Explain key benefits and challenges of different decision-making processes
- See relationship between decision-making process and trust, ownership and learning
- Use Advice Poker to create agreements about ownership of decisions
Managers, Executives, Scrum Masters, Agile Coaches
schedule Submitted 10 months ago
People who liked this proposal, also liked:
The Geek's Guide to People - Shifting from Output to ImpactSue Johnston
schedule 11 months agoSold Out!
The stereotype of technical professionals as inarticulate, socially inept geniuses inventing problems to solve is unkind and inaccurate. Yet the Dilbert image persists. So do jokes like the one about the engineer sentenced to death on the guillotine, who watches the instrument of death malfunction, then tells the operators how to fix it.
Why do people make fun of engineers? Do people wired and trained to analyze and solve problems and focus on the mechanics of a situation frustrate those whose brains are wired differently? And how does the engineer’s way of dealing with individuals and interactions - that first value of the Agile Manifesto - sometimes get in the way of team collaboration and productivity?
In this interactive session, we'll show a little empathy for engineers and other analytical folk whose neurological wiring makes them seem different from the rest of humanity. We'll also explore how those with the engineering mindset can develop their own empathy and consciously adopt behaviours that amplify their value to their teams and organizations, make them more effective leaders - and make their own lives easier by positioning themselves for understanding.
Join Sue in a lively exploration of what can happen when engineers and technical professionals shift their mindset from solving problems to creating impact.
You will leave this session with an appreciation of
- How to make your ideas meaningful to others by taking their perspective
- How shifting your language from "What?" to "So What?" helps people connect the dots
- Why giving up the need to be smart may be the smartest thing you ever do
- Techniques you can use to take someone else's perspective.
How to Reboot your Agile Team: The Secret Sauce!
Why do so many organizations struggle to put in place mature Agile teams that can apply proper Agile principles and deliver awesome products? Some people will say, “Agile is hard” as an excuse to not do Agile or to become frAgile. Well we think we have developed the “Secret Sauce” to rebooting any Agile team that just doesn’t seem to be maturing and we want to share it with you!
If you are thinking of scaling Agile across a large organization, then this talk is a must to attend to help ensure your teams have the right foundation. Organizations wanting to scale Agile must have a solid foundation of mature Agile teams who embrace the Agile values and have the right Agile mindset.
Over the years, as we have done Agile transformations in different organizations, we have seen common patterns that keep repeating. The most common pattern we found in our experience is that teams are frAgile. Too many either pretend to be Agile or don’t even know Agile is not a methodology, so organizations question the value of using Agile. Very often the confusion and frustration that comes with thinking that a team is Agile when they are not Agile, brings people right back to their old habits of command and control. Creating successful mature Agile teams is not sorcery, you need to discover the secret sauce!
In this talk, we will reveal our secrets on how to create a successful Agile-Scrum team in 5 sprints. Attendees will learn how we applied our secret sauce as we experimented with more than 30 teams and we refined the know-how. This recipe has proven to be successful in different organizations and teams delivering different types of products. Our Creative-Destruction approach goes through a human change process we labeled The Intervention Plan. The 5 steps are:
- Step 1: Run in the rain
- Step 2: Thunderstruck
- Step 3: Cry over the M&M’s machine
- Step 4: Open-up and look at the sun
- Step 5: Removing the training wheels
And by using these 5 steps, attendees will discover the 5th Agile value!
How to Get Your Whole Team TalkingGil Broza
schedule 11 months agoSold Out!
"Agile has too many meetings." "Our meetings are a waste of time." "It's always the same two people talking while everyone else is on their phones or laptops." Indeed, meetings are often pretty bad… but they are also necessary. Agile teams can't fully implement the 3 C’s (communication, collaboration, and consensus) only by inhabiting an open space or using a messaging tool. However, it doesn't take much to make a meeting effective, collaborative, and a welcome experience for its participants. Come to this experiential session to learn 10 simple changes you can make -- without having to become a professional facilitator -- to make your meetings matter.
From dysfunction to cross-function in 8,593 easy steps: Team building at the CBC
When it comes to scaling Agile, there is no one size fits all solution. Frameworks like Scrum and XP prescribe roles, events, artifacts, and rules that make it very clear how interaction should take place within a team. When we begin to add more teams to the mix, communication between teams becomes more complex. This complexity threatens to reduce our transparency and damage our culture. How can we share information, build our culture and work together, all while keeping with Agile values?
During this session Sam Lightowler and Jade Stephen will take an in depth look at the successes and failures of CBC Digital Operations when it comes to cross-team collaboration and information sharing. We will discuss what meetings and techniques have helped us build a one-team-one-product mindset, a sense of community, and a culture of Collaboration, Learning and Improvement. We will also discuss what we have tried in the past and how learning from those experiments helped us evolve into the agile-friendly and unified team that we are today.
Status and Power Improvtoddcharron
schedule 10 months agoSold Out!
Are you as powerful as you need to be? Do you over power the room and rub people the wrong way?
Why is that? What if there was something you could do about it?
In improvisation, in order to create realistic and compelling characters we study status. That is, how does how we carry ourselves impact our relationship status with other people and how does it change in relation to others?
In this session, we'll explore status, and play with making ourselves more or less powerful. We'll then examine how this plays out in our work environments and how we need to adjust our status depending on which groups or individuals we're interacting with.
You'll also learn the one status trick that will dramatically increase your chances of getting hired in your next interview.
Building powerful roadmapsGino Marckx
schedule 10 months agoSold Out!
Any organization’s ability to focus on what matters most to their customers is directly related to their ability to get valuable feedback from them. While more and more organizations embrace agile practices during the development of their services, they often lack in how they collect feedback and therefor don’t get the benefits they are after. After all, what is the upside to investing in being able to pivot, if there is no information available to guide the direction of that pivot?
The fact that many roadmaps leave little room for flexibility significantly contributes to this and building powerful roadmaps is a really hard task. How does one get feedback about a house without building it completely? How does one give feedback about a car without being able to drive it around the city for a couple of hours?
This session will provide you with practical techniques on how to build a powerful roadmap for your product or service, one that allows any organization to get valuable feedback from their customers. This workshop is based on ideas from the upcoming book ‘Thinking in Agile’.
Fixed deadline and 2 hour sprintsArdita Karaj
schedule 11 months agoSold Out!
It is common to work on projects that have a hard deadline. These deadlines are not always fictional and time really matters. Frequently, there is a big discussion if Agile is the right approach for these cases. Can we deliver what is requested without a detailed planing, task breakdown, milestones on a Gantt chart?
In this talk, I will bring examples from my experience volunteering at GiveCamp for several years. Over one weekend volunteers create digital solutions for non-for-profit organizations using 2 hour sprints, MVP deliverables, prioritization, collaboration and an environment in which you feel proud of what you do. If you think this can't happen in your organization, come to this session and challenge me!
Technical Practices through a Kanban LensNayan Hajratwala
schedule 1 year agoSold Out!
People in organizations that are learning Kanban quickly understand the relationship of WIP, Cycle Time and Throughput. However, when teams start doing things like Pair Programming, they tend to hold fast to the idea that “you’d get more done if you worked separately!”
High performing software teams use a variety of modern technical practices including Test Driven Development, Pair/Mob Programming, Refactoring, Evolutionary Design, and Continuous Integration & Delivery.
How do these practices fit into the Kanban context? Whether through improving collaboratively, evolving experimentally, or implementing feedback loops, learn how these technical practices are supported by Kanban's four Foundational Principles and six Core Practices, which in turn make Kanban more powerful.