There is a kind of employee every organization loves. They know which screen has the real number. They remember who to call. They copy the information from System A into System B.
They know the report is wrong unless you fix column G. They remember what happened yesterday. They translate between departments. They chase everybody.
They are indispensable. That sounds like a compliment. Sometimes it is evidence of system debt. If one person's memory is the integration layer, the company has built a very expensive API out of a human being.
This is one of the ideas I want you to notice as you start programming. The best first automation is often not the most impressive thing you can build. It is the boring thing somebody keeps doing. Quarterly reporting was an obvious example in operations. The organization already had the information. Then a manager would spend hours reconstructing it into a form somebody else could consume. Again. Again.
Again. If the system already knows when work was scheduled, started and completed, why should a human rebuild those timestamps? If it already knows how many jobs occurred, why count them again? If exceptions are recorded when they happen, why reconstruct three months of history from memory? Generate the baseline. Let the human explain.
Software handles repetition. Humans handle meaning. That distinction is useful when you design your own business. Think about every repeated touch. Customer asks for information. Customer receives information.
Customer does not respond. You follow up. Customer books. Preparation information goes out.
Work occurs. Customer receives completion information. Invoice. Thank-you.
Review request. Future check-in. That is a drip campaign even if no email marketing platform is involved. It is a sequence of states and touches. Now ask which parts require judgment.
A thank-you message may be generated. A complaint should probably not be treated as a normal marketing drip. A routine appointment reminder can be automated. A strange customer situation may need a person.
A receipt should not require creativity. A relationship sometimes does. The goal is not to automate humans out of the company. It is to stop spending human attention where a deterministic system can reliably carry the load. This is why I want you to learn scripts before chasing giant “AI” projects. A twenty-line program that removes fifteen minutes of stupid work every day can be more valuable than a dazzling prototype nobody trusts.
Look for repetition. Look for copying. Look for remembering. Look for chasing.
Look for the person who says, “Oh, every Tuesday I have to…” That sentence is gold. Then understand the process before automating it. What is the input?
What is authoritative? What transformation happens? What output is needed? What exception requires a human?
What should be logged? What happens if the script fails? Now you are not merely coding. You are designing an operating system around human attention.
And human attention is one of the most expensive resources in any business. There is a business version of this lesson that I would keep close. Every company is a collection of promises connected by handoffs. A lead becomes a conversation. A conversation becomes a decision. A decision becomes onboarding. Onboarding becomes delivery. Delivery becomes follow-up. Follow-up becomes either another relationship or a quiet ending. If one of those transitions depends on somebody remembering it at exactly the right moment, that is not yet architecture. It is hope. You do not need expensive software to fix that. First name the states. Decide what makes something enter a state and what makes it leave. Decide what information must travel with it. Decide which normal transitions can happen automatically and which exceptions deserve a human. Only then choose tools. Tools should implement the operating model, not become the operating model.
One of the things experience taught me is to respect the difference between a rule and the reason the rule exists. Rules make repeatability possible. Reasons make judgment possible. I want both. If all you teach is the rule, the first unusual condition can paralyze the person. If all you teach is judgment, every ordinary task becomes a fresh invention. The strong system has a boring normal path and an intelligent exception path. Normal work should move with very little drama. The unusual thing should become visible. Somebody with the right context should own it. The decision should leave a trail. Then the system should return to normal instead of making the exception the new permanent process.
Documentation belongs inside the work whenever possible. I do not want a team to finish operating and then begin a second job called “prove that we operated.” If a job changes state, record the state. If a decision changes the plan, record the decision. If an exception is resolved, preserve enough of the reason that the next person can learn from it. That history becomes extraordinarily valuable later. You can see where work dwells, which exceptions repeat, what changed before performance improved, and where a process quietly depends on one person's memory. Good documentation is not a pile of paperwork. It is the memory of the operating system. And keep some joy in it. Systems work can sound painfully serious when written in corporate language. In real life it is full of absurdity. Boxes go somewhere impossible. A tiny handwritten note becomes the seed of a giant process. The machine makes a noise nobody has heard before. A person solves something with a trick so simple everybody laughs. Somebody sends a six-word message that makes perfect sense to three people and looks like alien language to everybody else.
Those moments are part of why I loved the work. A complicated system is a puzzle that talks back. You make a change and reality answers. Sometimes it says yes. Sometimes it says absolutely not. Either answer teaches you something. The part I would want you to remember years from now is that competence is not knowing everything in advance. Competence is knowing how to find out. Establish state. Ask what changed. Find the constraint. Talk to the person closest to it. Check the evidence. Make the smallest useful intervention you can. Observe the response. Update your model. That loop works in a warehouse, a software project, a business, a classroom and a life. You are allowed to learn while moving. You just need enough discipline to know what you changed and enough humility to let reality correct you.
There is a business version of this lesson that I would keep close. Every company is a collection of promises connected by handoffs. A lead becomes a conversation. A conversation becomes a decision. A decision becomes onboarding. Onboarding becomes delivery. Delivery becomes follow-up. Follow-up becomes either another relationship or a quiet ending. If one of those transitions depends on somebody remembering it at exactly the right moment, that is not yet architecture. It is hope. You do not need expensive software to fix that. First name the states. Decide what makes something enter a state and what makes it leave. Decide what information must travel with it. Decide which normal transitions can happen automatically and which exceptions deserve a human. Only then choose tools. Tools should implement the operating model, not become the operating model.
One of the things experience taught me is to respect the difference between a rule and the reason the rule exists. Rules make repeatability possible. Reasons make judgment possible. I want both. If all you teach is the rule, the first unusual condition can paralyze the person. If all you teach is judgment, every ordinary task becomes a fresh invention. The strong system has a boring normal path and an intelligent exception path. Normal work should move with very little drama. The unusual thing should become visible. Somebody with the right context should own it. The decision should leave a trail. Then the system should return to normal instead of making the exception the new permanent process.
Documentation belongs inside the work whenever possible. I do not want a team to finish operating and then begin a second job called “prove that we operated.” If a job changes state, record the state. If a decision changes the plan, record the decision. If an exception is resolved, preserve enough of the reason that the next person can learn from it. That history becomes extraordinarily valuable later. You can see where work dwells, which exceptions repeat, what changed before performance improved, and where a process quietly depends on one person's memory. Good documentation is not a pile of paperwork. It is the memory of the operating system. And keep some joy in it. Systems work can sound painfully serious when written in corporate language. In real life it is full of absurdity. Boxes go somewhere impossible. A tiny handwritten note becomes the seed of a giant process. The machine makes a noise nobody has heard before. A person solves something with a trick so simple everybody laughs. Somebody sends a six-word message that makes perfect sense to three people and looks like alien language to everybody else.
Those moments are part of why I loved the work. A complicated system is a puzzle that talks back. You make a change and reality answers. Sometimes it says yes. Sometimes it says absolutely not. Either answer teaches you something. The part I would want you to remember years from now is that competence is not knowing everything in advance. Competence is knowing how to find out. Establish state. Ask what changed. Find the constraint. Talk to the person closest to it. Check the evidence. Make the smallest useful intervention you can. Observe the response. Update your model. That loop works in a warehouse, a software project, a business, a classroom and a life. You are allowed to learn while moving. You just need enough discipline to know what you changed and enough humility to let reality correct you.
There is a business version of this lesson that I would keep close. Every company is a collection of promises connected by handoffs. A lead becomes a conversation. A conversation becomes a decision. A decision becomes onboarding. Onboarding becomes delivery. Delivery becomes follow-up. Follow-up becomes either another relationship or a quiet ending. If one of those transitions depends on somebody remembering it at exactly the right moment, that is not yet architecture. It is hope. You do not need expensive software to fix that. First name the states. Decide what makes something enter a state and what makes it leave. Decide what information must travel with it. Decide which normal transitions can happen automatically and which exceptions deserve a human. Only then choose tools. Tools should implement the operating model, not become the operating model.
One of the things experience taught me is to respect the difference between a rule and the reason the rule exists. Rules make repeatability possible. Reasons make judgment possible. I want both. If all you teach is the rule, the first unusual condition can paralyze the person. If all you teach is judgment, every ordinary task becomes a fresh invention. The strong system has a boring normal path and an intelligent exception path. Normal work should move with very little drama. The unusual thing should become visible. Somebody with the right context should own it. The decision should leave a trail. Then the system should return to normal instead of making the exception the new permanent process.
Documentation belongs inside the work whenever possible. I do not want a team to finish operating and then begin a second job called “prove that we operated.” If a job changes state, record the state. If a decision changes the plan, record the decision. If an exception is resolved, preserve enough of the reason that the next person can learn from it. That history becomes extraordinarily valuable later. You can see where work dwells, which exceptions repeat, what changed before performance improved, and where a process quietly depends on one person's memory. Good documentation is not a pile of paperwork. It is the memory of the operating system. And keep some joy in it. Systems work can sound painfully serious when written in corporate language. In real life it is full of absurdity. Boxes go somewhere impossible. A tiny handwritten note becomes the seed of a giant process. The machine makes a noise nobody has heard before. A person solves something with a trick so simple everybody laughs. Somebody sends a six-word message that makes perfect sense to three people and looks like alien language to everybody else.
Those moments are part of why I loved the work. A complicated system is a puzzle that talks back. You make a change and reality answers. Sometimes it says yes. Sometimes it says absolutely not. Either answer teaches you something. The part I would want you to remember years from now is that competence is not knowing everything in advance. Competence is knowing how to find out. Establish state. Ask what changed. Find the constraint. Talk to the person closest to it. Check the evidence. Make the smallest useful intervention you can. Observe the response. Update your model. That loop works in a warehouse, a software project, a business, a classroom and a life. You are allowed to learn while moving. You just need enough discipline to know what you changed and enough humility to let reality correct you.
There is a business version of this lesson that I would keep close. Every company is a collection of promises connected by handoffs. A lead becomes a conversation. A conversation becomes a decision. A decision becomes onboarding. Onboarding becomes delivery. Delivery becomes follow-up. Follow-up becomes either another relationship or a quiet ending. If one of those transitions depends on somebody remembering it at exactly the right moment, that is not yet architecture. It is hope. You do not need expensive software to fix that. First name the states. Decide what makes something enter a state and what makes it leave. Decide what information must travel with it. Decide which normal transitions can happen automatically and which exceptions deserve a human. Only then choose tools. Tools should implement the operating model, not become the operating model.
One of the things experience taught me is to respect the difference between a rule and the reason the rule exists. Rules make repeatability possible. Reasons make judgment possible. I want both. If all you teach is the rule, the first unusual condition can paralyze the person. If all you teach is judgment, every ordinary task becomes a fresh invention. The strong system has a boring normal path and an intelligent exception path. Normal work should move with very little drama. The unusual thing should become visible. Somebody with the right context should own it. The decision should leave a trail. Then the system should return to normal instead of making the exception the new permanent process.
Documentation belongs inside the work whenever possible. I do not want a team to finish operating and then begin a second job called “prove that we operated.” If a job changes state, record the state. If a decision changes the plan, record the decision. If an exception is resolved, preserve enough of the reason that the next person can learn from it. That history becomes extraordinarily valuable later. You can see where work dwells, which exceptions repeat, what changed before performance improved, and where a process quietly depends on one person's memory. Good documentation is not a pile of paperwork. It is the memory of the operating system.