Suggestions
Deb Krizmanich
Chief Architect & Principal at Outcomes Work
Deb Krizmanich is a tech entrepreneur with a passion for empowering individuals and groups through transformational technologies. She started her career at IBM, where she helped clients embrace change and turned risks into opportunities. After co-founding a web-based healthcare company, she founded an NGO that executed large-scale projects in Africa and the Middle East. Finally, she designed, built, and launched Powernoodle, cloud-based software that leverages diversity to achieve engaged decision-making. Deb Krizmanich is a well-rounded professional with expertise in stakeholder engagement, decision quality, inclusion & diversity, behavioral psychology, cognitive science, international development, and change and transformation.
Highlights
Probably one of the most frequently asked questions I get from customers as they map their initiatives is "What is the difference between a Project Outcome and a Business Outcome?"
What are your thoughts? Is this how your organization differentiates them? If you have a different view, perhaps you could share your thoughts.
If you need more context for the terms: https://bit.ly/4akWeIT
The very thing that makes a diverse team a beautiful thing ... individual perspectives ... can also be the thing that wreaks havoc in a project.
I love how Simon Sinek nails the value of building diverse teams. We all bring different things to the table and can fill each other's blindspots and build on each other's strengths.
That same diversity can also cause chaos on a project. Try this .. at the beginning of an initiative ask ALL stakeholders (from the Board to the front line operations person to the solution provider) to write on a piece of paper or electronic sticky note what they think success will look like for the initiative.
Yep .. you will get as many diverse answers as there are stakeholders. Think about the chaos and impact on the project ... slow approvals, solution selection, implementation priorities and the havoc that ensues when the world changes mid-implementation.
That is why you need to bring all that beautiful diversity to the table when developing the Business Outcomes for the project and it's Business Outcomes Map. When everyone is involved in defining what success looks like (the Business Outcomes) you will be much more aligned and committed to that success.
