You are here

Lemurs and lions: why you shouldn't leap to implementors

Report: Early Strategy for Higher Impact
· ·
Don't just leap to the assumption that your issue is technical
cartoon-early-strategy-bad.png

One of the issues with the leap from a digital presence problem to talking to implementors is that somehow even the definition of success somehow gets morphed into whether it's a "good" technical implementation (like for example a cage that looks great and that is super-strong against keeping lions and people separate — or, in the case of a website, that it looks modern and follows standards rather than whether it is achieving broad business goals). In the case above, the lion is still aggitated but somehow everyone pats themselves on the back about the great cage. 

Of course, one of the reasons to avoid the assumption that you simply have a technical solution that needs implementing is that you might be blind to issues (like the lemur in the comic below). 

Better to deeply consider the broader issues for higher impact
cartoon-early-strategy-good.png

To tie this back to digital presences, the points are: 

  • You may be blind to the real issues your digital presence has (instead sticking with pre-existing ways of approaching and dividing your digital presence).
  • Some high impact changes require upper management input. 
  • Although this doesn't specifically come out in the comic above, many of these issues take time to even define — leaping straight to talking with implementors doesn't give you this time. 
  • There are a variety of non-technical issues (some people may even like the way that things work in a way that is ineffective, especially for site visitors).
  • Even the requirements for the technical implementation portion for your undertaking may require further investigation to reframe / define. 

Report: Early Strategy for Higher Impact

First published 30 January 2017