Why every project needs a benefit map

A common issue encountered on projects is that the project goals have not been clearly defined. A Benefit Map is a powerful visual to provide solace.

Digital transformation – organizations become living systems

I love to help companies shape their future architecture. Become customer-centric. Exploit digital technology. Integrate multiple channels. Help them provide consistent and ‘lovable’ customer experiences. To do this, we also need to reinvent our organisations and design them as living systems.

To boldly go further than changes in IT

What is a project? In its most simple definition it means implementing a change in a controlled way so that the investor doesn't need to take a leap in the dark. The word 'controlled' and 'change' are key in this simple definition. In this post, I’ll focus on our approach to define the way in which the business needs to change its way of working and how we leveraged our corporate process model to do so.

What is a project if not an epic journey

One thing we've learned from the first phase of the iHRM program is that a complete waterfall approach with one delivery moment, followed by an extended user acceptance period is not the silver bullet. For the second phase of the program, the scope is wider and the number of project teams is higher. In this blog post, I'll share some insights on how to effectively manage scope while going for an iterative and incremental development plan.

Yeah sure. How exactly are we going to do this again?

Previously I've pleaded for simple architectural designs that are easily understood by all stakeholders. This way the idea gets the support it needs. As a project evolves into the ICT design and development phase, both idea and design will need to be made more tangible. This is especially true when it comes to making it all work together. The purpose stays the same: to avoid ambiguity. The means? Keep it again as simple as possible by focusing on what really matters.