tl,dr: all business processes start somewhere, whether data, event or request driven. That simple goal is the starting point of request process improvement.
I just need to collect people’s email addresses to get started.
I get into a lot of solution conversations with my friends. This is consulting 101, but there’s more on the line when I’m personally invested in this person.
There are other challenges too, when it’s personal there’s usually a cost prohibitive budget, a.k.a. no cash on hand.
So when someone asked me how to collect information and “get started” a lightbulb went off!
All processes start somewhere.
It appears that almost all business processes come down to a click. An order. A bit. A byte. SOMETHING; whether it be data or a request, something triggers a business response.
Can we then assume that the best software gets this?
When I asked this, I re-asked it a couple times before I realized this was the value IT was providing. Particularly when it refers to Enterprise Architecture.
The decisions you make about the puzzle you are composing with technology investments influences your ability to react to information and events.
Which is why good architects and business analysts ask difficult questions about APIs and Integration points.
Can you send an example of the JSON?
It’s why great application developers know the details of how to alert and register events. As well as how to extract and parse event and alert information in a meaningful way.
How do you start a process? Is it as easy as filling in a request form? Do you click a button? Is it complex or simple? Why?
Participants in our second virtual hackathon have been challenged to start a business process. Create a simple registration application. Start capturing those email addresses and start the business process you need to start now.
For more information about how we feel about business processes check out this simple process flow, subscribe to our blog or check out who we are!
Cassy Lueneburg