Read a sample: 1. Work That Keeps Changing
You arrive at work expecting to continue a task you started yesterday. Before you open your notes, someone tells you that another team needs help. The new assignment sounds straightforward, but you do not know which instructions still apply, whether you have completed the required training, or whom to ask when you get stuck.
Meanwhile, the first team may still be expecting your work.
If this sounds familiar, the problem is not necessarily that you are disorganized. Rotating assignments create a particular kind of complexity. You may be learning the job while also learning how several groups communicate, set priorities, and pass work between people. Information that experienced coworkers carry in their heads is still new to you, and the person who explained a task may not be nearby when you need an answer.
A personal work system gives that information somewhere to go. It helps you capture what you have been told, notice what remains unclear, and arrive at your next assignment better prepared. It does not need to be elaborate. In fact, a system you can maintain during a busy day is more useful than a beautiful one you abandon after a week.
This chapter introduces the basic approach. You will meet a new employee who moves between teams, explore the common difficulties of changing assignments, and learn how three connected habits can help: recording instructions, tracking training, and preparing for assignments.
Just as important, you will see where your responsibility ends. You can organize your work and raise questions, but you do not have to make every priority decision or solve every staffing problem yourself.
Jordan is a new operations assistant at a company with several internal teams. Depending on the week, Jordan may help the customer support team update service requests, assist the inventory team with routine records, or join an administrative project.
The teams share some tools, but their routines differ. One team prefers questions in a group message. Another expects Jordan to ask a designated contact before changing a record. A third has a checklist for routine work but gives project updates verbally.
Jordan’s supervisor, Morgan, coordinates the rotating assignments. Team leads explain local tasks and provide guidance during each rotation. Jordan is still learning which kinds of work require specific training and where the official completion records are kept.
On a Monday morning, Jordan is finishing a support-team update when Morgan asks Jordan to help inventory later that day. The inventory lead mentions a record-cleanup task and says more details will follow. Jordan also remembers hearing about a training module related to the inventory system, but cannot remember whether it is required for this particular task or whether completion has been recorded.
None of these issues is a crisis on its own. Together, they create several questions:
- What should happen to the unfinished support update?
- What exactly does the inventory task involve?
- Is the remembered training required before Jordan begins?
- Who can confirm the answers?
Jordan does not need to guess. A short note and a few targeted questions can turn a vague transition into a manageable one. For example, Jordan can tell Morgan what remains on the support update and ask whether to finish it before moving. Jordan can also ask the inventory lead what the cleanup involves and how to verify any training requirement before starting.
We will return to Jordan throughout the book. The details of your workplace may be different, but the underlying challenge is common: doing useful work while the people, instructions, and expectations around you change.
A stable assignment gives you repeated chances to learn the same environment. You become familiar with the tools, the people who answer questions, and the normal rhythm of the work. When you rotate, you may have to rebuild some of that context each time.
The difficulty is not simply having more tasks. It is having more transitions.
A transition can interrupt your attention before you finish recording a decision. It can leave a task partly complete while the next team is already waiting. It can put you in a conversation where everyone else understands a term you have never heard. It can also make an ordinary request harder to interpret: “Can you take care of this?” means little until you know what “done” looks like and when the result is needed.
Different teams may also use different versions of the same word. A “review” might mean checking for missing information in one group and obtaining a lead’s approval in another. A task described as “urgent” may need immediate attention, or it may be urgent only within the requesting team’s workload. The label alone does not tell you what to set aside.
Training can be equally confusing. You might complete a general introduction to a tool but still need instruction or authorization for a particular activity. You might have attended a session without knowing whether a supervisor must verify it. Or you may be ready to work while the system access you need is still pending.
These gaps do not mean you are failing. They are signals that you need a reliable way to distinguish what you know from what you need to confirm.
A useful personal system cannot prevent every interruption or make every team communicate the same way. It can, however, keep small uncertainties from becoming invisible. Once a question is visible, you can bring it…