I’ve written quite a bit over the years on the value of using visual models and imagery to assist in conveying ideas and calibrating understanding with business stakeholders and delivery team members. While many have come to see the value of supplementing requirements documentation with visuals, many others still miss opportunities to fully leverage them, because they create them as a supplement to a requirements spec, often in isolation from business and delivery stakeholders, only involving others when they feel they have a fairly stable, draft product to present.
These models and visuals can and should be used as tools for eliciting requirements and driving to shared understanding; as ways to facilitate working discussions on topics for which we are seeking clarity. Start simple, start messy. Use the process as one of “collaborative creation”. When we draw on the whiteboard together – or model a process flow together – all parties walk away with the dialog and context for how we arrived at the end image. If we don’t see things the same way at first, we draw and discuss and deliberate until we achieve that elusive shared understanding.
The tacit knowledge – or knowledge that comes out in the dialog and sketching, but isn’t captured in the final documentation – is often a critical gap or missing link between business analyst and stakeholder that limits the success of our efforts.
I’ve found that the process of deliberating and rationalizing potential paths together with business and delivery stakeholders until we reach an agreed upon “best way forward” provides the real value in visual modeling.
Featured image via dnkbdotcom