NICOLE'S FIELD MAP ｜ PART 3｜SYSTEMIZATION
When I was young, I rolled out an ERP system at a tech company. That's when I learned: the hardest part of using a tool is never the tool itself. It's the people.
When you roll out a system at a company of any size, you're dealing with people of every age and every way of thinking. You have to get your logic into their heads before they'll use it. But what's good for the company isn't automatically good for them. They think: "My old process and my skills work fine. Why should I use this thing you're giving me?"
AI is the same today. Getting every employee to use AI agents and workflows takes time and a push.
Systemization means connecting people, processes, tools and rules into one whole so work can be repeated, handed over and tracked. The simplest test of whether a company is systemized: if someone takes leave or quits, does the work still run normally?
Figure 1｜Four parts of a system
Peter Senge introduced "systems thinking" in The Fifth Discipline (1990): look at how things connect rather than at single events. One promise from sales can become work for the warehouse, accounting and customer service, which is why systems have to be seen as connected.
Michael Gerber, in The E-Myth (1986), points out that many founders start as skilled "technicians," great at landing customers or making products. Once they open a company, they need the skills of a "manager" and an "entrepreneur." His advice: don't just work in your business; work on it, in other words, spend time designing how the company runs.
Figure 2｜People adopt new tools at different speeds
It also explains why "the system went live but nobody uses it": it's not that employees won't cooperate, it's that everyone adopts new things at a different pace.
The people. That's why I believe leadership matters. Leaders need to communicate clearly with every department head and be clear about why they're doing it: because the market is using it, or because the company truly needs it?
People need to accept it first, then understand it, then see what's in it for them. The structure has to be very clear, with a framework that shows everyone how to use the system properly.
The goal of a system isn't to add work or friction, or to follow the market. It's to cut costs and raise efficiency so everyone can move one step further.
I hit that stage myself too. When time is short, resources are thin or priorities don't line up, people start to feel the system isn't that important right now.
That's why you need regular, measured sessions so everyone absorbs the system the same way and builds the habit. It really takes time.
I don't think so. There are many kinds of systems: workflow systems, platform systems, ERP, CRM. Being systemized doesn't mean having everything in place; it means fitting your situation: add the tools you need now, in stages, so the team can keep moving.
Besides people, timing matters. Everyone is using AI agents now, and owners get anxious. But some companies move slower, for example because of internal data, they're slower to bring in their own AI applications. In return, their risk is lower and protection higher。
Workflows, staff collaboration and supplier collaboration are all just tools. Their value is helping you get things right every time and giving you good data and execution.
Honestly, I'm not a sales-driven owner, and they're more hands-on than I am. But looking at sales itself, what they overlook most is "no time": they have to find clients and serve clients, and their schedule is packed. They think: what's in this system for me? Will sales go up? Will my bonus?
The fix is to think a bit more on their behalf. If you have resources, assign someone to remind them; if not, connect your workflows so the system notifies them, reminds them to use it and report progress automatically.
People learn differently too. Some want videos, some want written steps, so give them both. But in the end it comes back to the leader: you have to tell them this really matters. When you look out for them, they look out for you.
My structure is actually simple. I'm not someone who wants everything I see; my wants are few.
Every October to December, I plan the next year's marketing strategy: from big direction to small, annual, quarterly, monthly, down to the smallest details, all laid out clearly, along with who's responsible for what.
Plans change, of course, and new things get added. But anything I add has to improve efficiency. This second half of the year, for example, I brought AI agents into my work, in the cloud and on my computer, to make things more efficient, not more complicated. I don't do complicated things, so everyone can reach their goals with more freedom.
Both the brand side and the service side have blind spots. On the brand side, your attention goes to revenue, targets, project management and team communication, and it's easy to forget the outside world.
My advice: meet and discuss often, but don't rush or pile on pressure. You can bring in someone from outside, or have people suggest improvements to each other. When no one has time, put up a work board or a daily log and record things regularly.
Inside or outside, give yourself some breathing room to see what still needs filling in. Every company has its own pace; if an outside consultant pressures you, just tell them. We all understand your limits and your stage.
A system isn't for following the market or making things complicated. It's for cutting costs and raising efficiency so the team can take one more step.
You don't have to systemize everything at once. I suggest a yearly rhythm: lay out the structure in Q4, then roll it out in stages next year:
Figure 3｜Building structure on a yearly rhythm (Nicole's approach)
| Self-check | Yes | No |
|---|---|---|
| If someone takes a week off, work still runs normally | ☐ | ☐ |
| Key processes are written down or recorded, and new hires can follow them | ☐ | ☐ |
| Decisions follow rules, not the owner's mood in the moment | ☐ | ☐ |
| There's a fixed time each month to review numbers and progress | ☐ | ☐ |
| Before adding a new tool, its purpose and benefits are explained | ☐ | ☐ |
Systemization means connecting people, processes, tools and rules into one whole so work can be repeated, handed over and tracked, and the team moves forward without the owner watching. ERP, AI and messaging apps are just tools within it.
No. Tools are only part of a system. Nicole Chen believes systemization should fit your situation and roll out in stages, starting with people: help employees accept it, understand it and see the benefits, with the goal of cutting costs and raising efficiency.
People adopt new things at different speeds; according to diffusion of innovations theory, early adopters are only about 16%. Leaders need to explain the purpose, offer different ways to learn such as videos or written steps, and practice regularly.
The simplest check: if someone takes leave or quits, does work still run normally? Are decisions based on rules or on the owner's judgment in the moment? Regular meetings, a work board or daily logs can also show what's missing.
Further reading
Not sure where you're stuck?
I won't tell you what to do. I'll tell you what you're missing.