Things We Do Not Do
… we prevent a planned success make things worse
Go2Cab has a list of Things We Do Not Do. The “we do not do” is a list of classical methods used to undertake the “as is”, “to be”, gap analysis, the construction of operating models, roadmaps and the like. Unlike the traditional methods, Go2cab Evidence Based Decision Making framework avoids wasting Client’s time when undertaking business transformation.
Wasteful Workshops
Things We Do NOT Do include:
>> Go2Cab avoids wasting Client’s time during business transformation.
>> We do not tell what you already know.
>> We do not ask classical questions and forget (or ignore) asking the right questions.
>> We do not collect numerous posted notes with content that has little or noting to do with addressing your real pain.
>> We do not author ambiguous, non-traceable or non-testable business or solution requirements that may look cool but neither add value to your “Value Chain” nor make sense when compared with your desired targets.
Misleading Statistics
In cases where reports become evidence, such facts are no more than a visualisation of raw count, averages and percentages over time. We have seen Clients trapped into using the wrong evidence, be it data collected or, presentation of bubble charts or heat maps as a consolidated outcome of the situation. Ironically, one of the mistakes is treating categorical data is mixed with numerical data. Another common mistake is relying on the height of a bar or percentage to reflect the significance of the topic which is almost all cases, the latter will mislead the powers to be.
Confusing Workflows
Another “We Do NOT Do” is drawing procedural-like workflows where the majority of Clients are ill-advised to start with the “as is” situation. For a start, neither the facilitator nor the audience has the knowledge of the best practice. The sessions turn into gathering opinions and issues discussed lead to a confusing “workflow”. The outcome is then generalised to topics representing the inefficient operation such as Communication, Stakeholder Management, Lack of Automation and Reporting. Such topics are the same regardless of the domain. People ignore the details in an attempt to simplify the situation so that workflows are drawn using some notation or a “magic” tool as if the notation or the tool will sort out the organisational issues. No one asks questions like “Do we really need this part or that process”. The louder voice is typically the winner!
