Discovering the universal Business core

What should Enterprise Software do if it stopped wasting everybody's time supporting the work to allow real work instead of supporting real value creating work?

Obviously, it should directly support the work that actually creates value. If it did that, much of the work to allow work would become irrelevant and much resources could be freed.

Over the last few years I've been busy analysing all kind of businesses, and in many cases built models thereof on our Enterprise Software platform.

 

Slowly but surely, like peeling an onion, it seems that I've found the core. A core that could model any business.

And that's pretty important, with a generic business model the step to a code based model is short. That could lead to a process based IT system that could run any businesses. Or government, health or education organisation.

This model can make the ubiquitous Barely Repeatable Processes repeatable, structure the unstructured processes, tame the untamed processes:

1. Everything starts with one of three instigators: An issue, an idea or a request. A customer calling, an idea that hits you in the shower, a patient with a broken leg, perhaps some observations in the field, sudden drop in sales figures or a new survey landing on your desk. Register that and you have the start of a value creating workflow.
2. That will lead to a first level of assignments, to yourself or others, that might be termed "research" or starting with "please find out...".
3. With results in from that first level of activities you can now discuss it, even ask pointed question to specific people you might think have valuable input. An asynchronous version of a meeting - "Peter, what do you think about...". Or even have an old fashioned meeting with donuts as a single task assigned to whoever you'd like as meeting organiser.
4. As the issue, request or idea starts accumulating good and bad solutions, you'll get closer to the point where you and perhaps some others will make a decision: This is the best solution, lets implement.
5. With that, another multilayer set of assignments will happen. As assigned tasks are ticked off, new levels of sub and sub-sub tasks are assigned then finished off, something that looks and behaves like a 'project' unfolds. Until all done, solution implemented, leg plastered or a new product designed and set in production.

Converted to code, it would function like this Work Processor, no rules, no limits:

8 minutes simple process demo.

Comments

[Account Deleted]

This sounds familiar! Nice video, by the way - my next step is to use the builder to extend the model you sent ...