Nestled in each of these statements is a description of the motivation for the envisioned change or needed solution. The envisioned end result exists to bring about some desired future state.
Captain Obvious stuff, for sure. However, my guidance is directed at the more fledgling officers who so easily and routinely fall into the following easily avoidable pitfall.
Beware of the Pitfall of Using Solution Language
Now, consider the following cross-checking questions as it pertains to these statements:
Now, imagine you are a solutions designer trying to solve for one statement or the other.
A designer's choices are severely limited by statement #1 whereas statement #2 leads to further exploration in discovering important notions that drive design clarity:
Lieutenant, with All Due Respect, People Matter
Users want solutions that cater to them. Not all users own iPhones...now or in the future. If you bring them a solution that does not respect who they are, it will not resonate with them and will ultimately not be a viable solution to their problem.
Solution designers want a clear description regarding the problem, who it affects and what the envisioned benefits of the ideal solution entail. Thy need this so that they can define a solution with respect for who it is for and how it affects them. If you bring them a solution statement, you have disrespected their opinion.
Don't disrespect users and solution designers by leading them by the nose to your envisioned solutions.
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 hope you'll join us.
So, What's the Problem?
When organizational leadership mandates transformational change from on high at an accelerated pace, it often does so without respecting the complexities required to describe the problem space and design the solution. The resulting underestimation of effort creates a pressure cooker atmosphere for those tasked with designing and creating the future state in a hurry.
The resulting solution design efforts are staffed and funded with fewer resources with a shorter window of opportunity to define and describe the ideal future-state process design.
What's In Your Agile Designer Toolkit?
The demand for accelerated change is pervasive. Responding to it requires an effective, efficient means of defining the problem space so that solution designers can create a future state solution that delivers value by actually solving the problems people are experiencing.
This is the context in which the spirit of agile design thrives.
As a business analyst or solutions designer operating in this space, it requires an approach where defining the problem and designing the solution need to be done with a minimalist's acumen.
Developing an agile design perspective and related set of techniques, rituals and practices really helps in this future-state design wheelhouse.
So, I'm reaching out to my fellow practitioners. What's it like in your world? What's in your agile designer toolbox? How's it working for you?
I look forward to hearing from you.
Subscribe to my free blog updates to receive content that vividly describes the techniques and leadership skills that embody this 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 for the journey.
I help organizations design solutions collaboratively using agile design methods leveraging my vast experience in survey software solutions, enterprise architecture, business analysis, Pragmatic Marketing, user experience design and performing in musical ensembles.
Free Updates by Email