11 best practices for designing a data-driven organization

In part one of this post, we broke down the decision-making process for running a data-driven organization in an attempt to understand how KPIs can be weaponized in the wrong hands. Once the fundamental forces of how data influences perception are understood, the next step is to understand how these forces can shape the decision-making process in your organization to act as friction-reducing agents that can propel your organization into next-level decision making speed.

Why all API consumer journeys need a map

In the previous blog entry, I described two specific design artifacts (user types and personas) that can be used to inform an intentional API consumer experience. In this entry, we’ll go one step further into the API ecosystem and map out how the consuming developers (i.e., the direct users of the API) work with other user types to achieve their goals. Understanding how all the players come together to support your API consumers is fundamental to developing the right API product as well as the right set of services and support offerings to make your users successful.