<aside>
📌 Welcome! 🗺️ Outcome Model is a tool that can help you create a ‘system’ in your work. By having a system, you work smarter, not harder.
</aside>
To build great things, you need to work together. But working together in organization, is hard.
You just can’t simply delegate things and done. That’s the hard truth. The work quality sometimes hit and miss. You need to regularly ‘fix things’. Everything seems relied on you. So you tried productivity hacks and supplements. It works! Until it didn’t 💀. You somehow work 3x harder, even though you have now bigger team in the organization. 😮💨
“Successful organizations, are the ones who can run by themselves.”
Well the solution is, you need to build a system. What is exactly a system?
So basically, what you’re doing (writing, animating, handling project, selling, etc) are repeatable tasks. They have 1-2-3 steps right? By documenting your 1-2-3 steps (and later hire people to do the stuff for you), well that is a system!
But system can be anything from one pager (that is unhelpful) to 100 pages of book (that is too much, cmon!). So let’s make our lives easier. In this wiki, we’ll learn how to create a system that is simple, easy to read and visual!
“Start with the ‘end’ in mind.”
The four process of outcome model.
We call this format as 🗺️ Outcome Model. It’s called like that, because when we’re making a system, we will need to define our end goals (or ‘outcome’), first and foremost. This model is basically a visual flow chart tool that can help you understand what you’re doing everyday in your job, in a big picture.
Here’s an explanation for the each process:
| Parts | Description | Example (🍔 McDonald Burger) |
|---|---|---|
| 👷♀️ Input | Resources and activities that is needed to create your product/services. It can be resources like personnel, raw materials, tools. Or it can be activities like training, techniques, routines. | 🧑🍳 Chefs, 🤵♂️ Waiters, 🥙 List of ingredients, 🍳 Kitchen tools, 🧠 Staff training |
| 🛠️ Activities | 1-2-3 steps that is needed to create your product/services, from start to finish. The activities should cover the steps from the very beginning, until your product has arrived on customer’s hands. The activities can be short, or long, depend on your products. Producing a burger and a plane is vastly different in steps. The general rule is to always build the steps from general (pillar) to specific. Just like the McDonald example in the next table, the steps are simplified to four general steps. But you can breakdown / make a detailed steps on each ones. For example, you will list down 7 steps on ‘Cooking the burger 🍳’. | 1️⃣ Preparing the ingredients 🥙 |
| 2️⃣ Customer order 🧾 | ||
| 3️⃣ Cooking the burger 🍳 | ||
| 4️⃣ Delivery (dine in/takeaway) 🍴 | ||
| 📦 Output | The product/service itself. If you have many different products, you need each to have their own outcome model. | 🍔 Big Mac |
| ❤️ Desired Outcome | The targeted standard of your product/service to the customer. Targeted standards here means you need to insert some quantitative standards (served in 2 mins, that can run 120km/hour) or qualitative standards (tasty, good looking, prestigious) to your products. It depends on your brands and product differentiation strategy. To understand this deeper, read this ‣. | 🍔 Tasty Big Mac burger as advertised, 🕑 ready in 2 minutes |
Here is a guide to use 🗺️ Outcome Model efficiently:
👨👦👦 Working backwards Everything start from the customer. At the end of the day, they are your true boss. That’s why, you need to define the desired outcome first, then output, then activities and the input. What kind of standard do they accept in your product? Write that down on your desired outcome. Remember, customer don’t really care about your under the hood stuff (most of the time), customer ONLY care about what you serve on the table. When you buy an iPhone, you just want one that works. You won’t really care about Apple’s complicated production stuff right?⚙️ Do it on repeatable tasks If your works happen only once, don’t build a system. But if your works will happen for months, years, or forever, build a system. Set the goal — that someday — the system can still work well without you participating. if you help an organization grow, there will be more room for you to grow your career also. (e.g you’ll be stuck as music engineer for 5 years, as there’s no more room to grow in the company). By having a great system, you will have generally more free time also. It means, you can spend your time more on things that you like, spend more time on your hobbies, or taking up new projects in the organization for learning up new skills.📦 Aim for predictable results A well-defined system should have predictable results. Imagine a production line in McDonald's - each and every step is specified in detail to produce the same output. If followed correctly, the result will be the same every single time — no matter who follows the process. If you still see big swings in product standard, try adjusting your input and activities, until it gets ‘right’.