The process to create processes

[RazorCut]

What're the resources to learn how to create business processes / routine / systems?

You'll need to expand on that. Processes are just that. Creating processes just for processes sake are useless and just action faking.

You only create a process, routine and system to solve a problem, automate something or create a specific flow.

What SPECIFIC issue are you trying to solve? If you don't have a business yet then you don't need a process you just need to discover pain points and test if the market are willing to pay you to provide a solution.

 

[Andy Black]

Processes start by being ad-hoc actions taken to make something happen.

If you keep having to make the same thing happen then you’ve identified a new process.

You may want to document it for your future self or someone else to repeat.

Except being documented doesn’t make it repeatable. Make sure someone else can step through the process documentation. Only then is the process repeatable.

Some or all of the process can be automated. Just don’t try automating too soon (aka before you’ve done it by hand a few times).

The final stage is optimisation.


So the life-cycle of a process is:

1. Ad-hoc
2. Defined
3. Documented
4. Repeatable
5. Automated
6. Optimised

 

Dislike ads? Remove them and support the forum: Subscribe to Fastlane Insiders.

[ryanbleau]

I used to write SOP for a government agency and now I design processes for a tech company. IT's just one aspect of what I do but it's a big part. Processes can be the easiest thing you can create or the worst thing you ever did. Lay out the steps and let someone else do it. easiest way to see if its a well thought out process.

 

[ZCP]

Read Emyth by Gerber as a start. Then come back and ask better questions. Then hire consultants if needed. Spend your time selling.

 

[abogdan88]

What're the resources to learn how to create business processes / routine / systems?

 

Dislike ads? Remove them and support the forum: Subscribe to Fastlane Insiders.