
Improve (what will you do differently?)
This is the critical step that is missing from most improvement efforts. This is where you highlight how you will improve your outcomes by changing how you undertake processes. This can mean a couple of things:
- Repeat the process (and fix the problem). Sometimes, the new skills and knowledge you gained the first time around will will help you fix the problems you encountered. This is the best option when there is clearly a mistake that was made and can be fixed the next time round.
- Dedicate more resources to the process. This applies in two situations. The first is when a process isn’t working because it hasn’t been properly resourced. If the process isn’t working because not enough time, money and resources have been spent on it, this might be the best option. In practice, it’s rare to double-down on failing processes. The second situation is when a process is working and you’re reinvesting in its future success. It’s usually a good idea to invest more time and effort into the things which are working.
- Stop the process. This is an obvious solution for processes that are not working. If something is not cascading into the next level (e.g. tactics affecting strategy), it’s usually best to kill the tactic. Unless you have sunk considerable costs in the process*, have identified a clear problem that can be fixed, or plan to allocate more resources to the process, the best idea is to stop doing it and allocate your limited resources elsewhere.
- Try a different process. Another method of improvement is to try something new altogether. This is the riskiest and, unfortunately, the most common option. It’s also the option least likely to succeed.
If you have tried something before, you have learned a lot about what makes it work or not work. You’ve made progress towards finding the right answer. You’re more likely to succeed the next time. In practice, it’s usually easier to spend more time on things that are working than to try something new. Trying something new means starting from scratch on something you haven’t done before.
|
Working |
Not Working |
| Easy benefit from extra resources |
Allocate more resources |
Fix the process |
| No benefit from extra resources |
Repeat the process |
Stop the process |
You can see the clear choices before you.
You might notice that, so far, we haven’t talked about what analytics package to use or how to set up a dashboard. This is deliberate. It’s far too easy to dive into any analytics package (Google Analytics, Omniture, Community-Analytics, etc.) and find a bunch of data that’s interesting.
But ‘interesting’ and ‘useful’ are polar opposites on the value continuum. You can spend hours looking at interesting data believing you’re making headway. Try not to do this. Don’t ever open an analytics package unless you know exactly what you’re measuring and how you’re going to make your analysis. Then, once you do open it, ignore everything outside of this scope. This is simply noise.
Measuring What Matters
Far too frequently we jump into Google Analytics and begin measuring a whole range of things which really don’t matter much. We measure visitors, users, time on site, bounce rate, goal conversion and more. None of these matter unless they fall within the framework above.
With this in mind, it’s time to define what you need to measure.
* Sunk costs are usually a terrible influence on decision making. They often lead to sending good money after bad money. Here, it is whether the time and effort invested in executing a tactic (e.g. building relationships, establishing skills, etc.) would save you time compared with a similar tactic.
Share
Facebook Facebook
Twitter Twitter
LinkedIn LinkedIn
Google Plus Google+