Hopefully, ‘Yum! That looks delicious!’
Or maybe it doesn’t look too good, and you’re wishing you’d chosen the same thing as your dinner partner.
Either way, what’s sitting on the plate in front of you immediately sets a positive or negative impression.
MasterChefs know this. They don’t go to all that trouble with presentation for nothing. They understand its importance.
They understand that the way food is presented is just as important as the way it tastes.
So when you’re documenting your business processes, how much thought do you give to the way they’re presented?
Because the way you present a process is just as important as the way you’ve explained it. Continue reading
I was at a meeting with a client (a big Aussie company), presenting the draft of a document I’d just completed for them. We (that’s me and the team I wrote the document for) were at the stage of socialising the document within the organisation.
Considering what was presented, I was somewhat taken aback (to put it mildly) that the comment about the document’s length was the first piece of feedback we received.
Unfortunately, lengthy documents immediately set expectations for readers — negative expectations.
So how long should a document be?
Well, how long is a piece of string? Continue reading
Harsh, yes, so allow me to explain …
As a means of mapping a process, socialising and refining it, and as a visual representation of it, flowcharts are hard to beat. They make processes easier to define, understand and follow.
But as the final documented form of processes, flowcharts aren’t always effective.
It’s not flowcharts, per se, that are the problem. It’s that, often, they’re poorly drawn.
And that’s why I hate flowcharts. Continue reading