Adjacent Possible

My humble opinion, on the only way to error proof and measure a process consistently. 

How to understand one of the components I would use, in execution of a total quality management  architecture design?

Build for the rule and allow the adjacent possible for the functional business architects.

Present the right things first! Then allow a user, to make decisions to explore within the adjacent possible. Versus, opening the entire house and expecting people to know what's right and then tell them later it's wrong when it needs to be right.

Food for thought.

Data Governance and the Adjacent Possibleocdqblog.com

I am reading the book Where Good Ideas Come From by Steven Johnson, which examines recurring patterns in the history of innovation. The first pattern Johnson writes about is called the Adjacent Possible, which is a term coined...

1 comment

Syed Suhail                       

Lisa,

Thanks for sharing the "Data Governance and the Adjacent Possible" article. I completely agree that the pattern "Adjacent Possible" is a good way of thinking to implement a business architecture program as well. I have been involved in similar situation where data architecture was a mess and there was no data governance. We started building data governance business capability brick by brick. We created a list of tasks that become part of daily guidance for business data stewards. These stewards started participating in a new initiative review process to ensure , for example, master data (e.g. customer, provider, citizen, supplier etc) is properly defined and reused across multiple initiatives. We attacked one business area at a time, we fixed this area and then moved on to the next. In some cases, it was not about fixing the master data but to implement certain data policy to fix the quality of data. We did not open the entire house, we fixed one room at a time.

Syed

5 days ago