Our blog

An independent, outcome focused guide Why do the business and technical sides of an organization so often frustrate and disappoint each other? This is the last of four articles in which I explore that question, along with some possible solutions. You can save a lot of pain and considerable expense by having someone on the project leadership team who deeply understands both the technical aspects and the strategic business objectives, and who can translate fluently between th

Invest in clarity Why do the business and technical sides of an organization so often frustrate and disappoint each other? This is the third of four articles in which I explore that question, along with some possible solutions. Building management dashboards has become common practice in organizations. Ignoring them is almost as popular. Most of us have seen the dashboards that go unused because they were poorly conceived to begin with. We don’t have to tolerate this wa

Business and tech approach problems differently Why do the business and technical sides of an organization so often frustrate and disappoint each other? This is the second of four articles in which I explore that question, along with some possible solutions. Business teams focus on the outcome, while technical teams focus on the problem. This separation results in two very different approaches to problem-solving. And that can seriously handicap effective collaboration bet

The gap between technical and business Writer Ambrose Bierce once defined a conversation as “a vocal competition in which the one who is catching their breath is called the listener.” If you have ever sat in a meeting between technical and business teams, then you have seen his definition in action. Unfortunately, the real-life consequences of this miscommunication can be anything but funny. Why do the business and technical sides of an organization struggle to communicat

How to recognize what’s optional Nothing determines the success or failure of a project more than the quality of the requirements you develop at the beginning. It really pays to invest time getting them right. There is something reassuringly certain and fixed about the term “requirements.” But real life shatters that illusion pretty quickly. Minds change and new information emerges, so you have to adapt the requirements. The term “requirements” then is a bit of a misnomer –

When the data needs to be right If your business uses modern analytics tools, you have probably noticed that your vendors are rushing to add AI to their solutions. But it’s not clear that the tools are really driving better results. At Analytics Strategies we have seen that there is usually a large gap between what the data says and how it is used to drive decision making. This gap becomes a chasm when implementing many AI solutions since there are even more questions abo