..or, "how to reduce 20 years of modelling into 5 bullets". If you need to explain to someone what we do, try this short explanation.
Explaining the idea of 'modelling' to non-modelers
On my last holiday, in between soaking up some rays and watching the sun go down over the ocean, I got around to reading some of those books that have been on the ‘must read’ list for months.
And even talked to the family for a change. One conversation started with ‘Dad – what do you actually DO‘.
This is a tough question when your life is spent manipulating ideas around a screen, and trying to understand how businesses want to work. All a bit abstract.
So this is what I came up with:
- We capture what we’re trying to think about in a rigorous form. Our ideas may start out as a Mind Map, but the blobs on the picture get quickly morphed into more definite things: Risks or Requirements, Domain concepts or processes, States or Business Functions, not just paragraphs of text.
So no Blob and Stick diagrams, and no more Visio.
- We put those ‘things’ into some kind of tool. This is essential. What we’re grappling with here are problems which larger than will fit into a single head, so we out-source the remembering to a computer *.
- We think hard about the relationships between the ‘things’. Just like the WWW, it’s the links which provide the richness. So a Business Goal and a User Story are interesting ‘things’, but if we connect them together by saying ‘this User Story contributes to the achievement of the business goal, we start to add more value to the problem.
- We use the modelled ideas, and the tool where they sit to help us to do a better job of analyzing.
- “This User Story doesn’t connect back to any project objectives? What’s it doing in scope?”
- “Why do we have a stakeholder who does’t appear to be responsible for any Requirements? Did we miss something?”
- “Have we implemented all the local security requirements somewhere in the solution?”
- We treat the model as an important organisational asset. Over time, the model will contain more and more knowledge about how and why our organisation works. And we’ll have spent thousands or millions of (£/$/€) creating it, so we’d better look after it, and make sure it gets used by every project, but also stays consistent and useful.
So that’s it in 5 bullets.
(* the idea of ‘outsourcing the remembering’ came from a holiday reading book ‘The Organised Mind’)
More Learn Options
Model styles for processes
19 February 2021
Process models are hard to maintain. Maybe that's because they have poor structureLearn More
Where to start modelling
18 February 2021
Faced with an empty model and a problem to solve, where should you start?Learn More