The Archieve of CONSEQWIN

Conseqwin is a project my father and I are developing together, exploring how service-management knowledge could become something people actively practise.

A course can explain a concept clearly and test whether someone remembers it, while leaving room for a different kind of learning experience. I’m interested in what happens when the learner encounters a situation without being told which concept applies, particularly when there are reasonable arguments for more than one response.

That is the direction we are exploring with Conseqwin .. scenarios in which people make decisions and examine what follows. The opportunity lies in making those decisions substantial enough that someone has to interpret the situation, rather than recognise the wording of an expected answer.

Consider a service interruption where a temporary workaround could restore operations, but its limitations are not fully understood. A learner might choose to proceed, investigate further, or seek authorisation. The useful part is understanding what would justify each response and how changing the circumstances changes that judgment. Simply adding a story around a multiple-choice question would leave much of that opportunity unexplored.

That is where I connect product design with the business model. An individual practising independently might value access to scenarios with explanations they can revisit. A team could get more from working through the same situation together and discovering why colleagues made different choices. An organisation might need scenarios adapted to its own responsibilities and procedures, where the discussion relates directly to how its services operate.

I see these as possible offers to validate as we develop Conseqwin. Each would need a clear purpose and a reason to exist beyond putting different prices on access to the same material. A facilitated team session, for example, would need to offer something that independent practice cannot which is the opportunity to examine disagreements and work through their implications together.

There is also a practical question about how those offers could support a profitable business. A reusable scenario library could form a shared foundation, while facilitation or adaptation would require additional work. The pricing would need to reflect that difference, including the ongoing effort of reviewing scenarios and keeping their reasoning credible. An attractive contract would be less attractive if every delivery required rebuilding the experience from scratch.

This makes deciding what should be reusable part of the product design itself. I would want to preserve the underlying decision logic where it remains relevant, while allowing the context to change meaningfully. That could make it possible to serve different situations without losing the care that makes a scenario worth using.