Why Encoded Insight?

When you encounter a company with a name like “Encoded Insight” you may be expecting that the company delivers industry proven insight based upon established experience accumulated over decades. This established experience informs you on the proper way to run your business.

There is a place for this fundamental perspective. However, this approach alone is overlooking a rich repository of insight.

The insights you have developed about your business.

These insights have been incrementally built up over time and are unique to you and your business. No one else has developed the exact same insights. No one else has faced the exact same decisions. The ability to make proper decisions for your business comes from not just facts and figures, but a strong intuition.

Only after these insights are understood can the conversation be had about encoding your business through software. For a business to reach its full potential the insights of the business have to be translated into processes that can be owned and executed independently. These processes are a blend of standard procedures, timely data, and software.

Attempting to design software without an understanding of the core business can be frustrating and costly for everyone involved. A deep understanding of both the business and software are required for an effective translation from one to the other. The value is in the bridge, the combination of the two. The goal is not to replace your insight but to encode it.

This is not an easy bridge to build and many people shy away from it. There are many questions that arise as we dig deeper into what it means to translate your business insights into software.

• What does it mean to build a bridge from software to business?

• Is there a common language that can transition concepts from business to software?

• What language should be used to translate software engineering concepts to business?

• Are we effective at encoding the insights people have accumulated about their business into defined processes?

The only way that these questions will be answered is for you to help me iterate on my own insights. These posts, along with short thoughts on Twitter, will be how I communicate my evolving understanding of what it means to encode insight.

I’m @EncodedInsight on Twitter, feel free to reach out with feedback or insights of your own.