Findability is surprisingly complex due to the large number of measures needed to be understood and undertaken. I believe that one of the principal challenges lies within the pedagogical domain. This is my fifth post in a series of simple tips for reaching Findability.

Effect driven development!

Most projects are undertaken to achieve operational improvements in an organization. An often relied upon truth is that IT driven, or what I’d like to call “feature driven”, projects are more likely to fail than projects with a clear focus on business benefits. Many pitfalls can be avoided by using a structured approach while making business benefits the centre of attention.

An excellent tool to keep focus on satisfying real business needs, rather than developing features only few will use, is Effect Mapping developed by InUse AB. The basic idea in this method is defining what actual business effects should result from a project, as well as identifying target groups contributing to these effects and their specific needs. It is all visualized in a so-called Effect Map.

The Effect Map is a great tool for communicating goals and means needed to achieve them. It can be used throughout an entire project to manage changing requirements, keep the business in focus and prioritize what really matters; all while new knowledge is gained.

Development of an Effect Map takes place during a series of workshops, providing valuable insights to any project. It is especially helpful in Findability projects, as they span many different parts of any business, from managing information and the organization to technical solutions.

A good strategy used in conjunction with an Effect Map and long-term goals provides you with a great starting point for succeeding with your Findability. You can read more about different approaches to building the business case in this blog post!