My first year at a small agency was a blur of things going slightly wrong. A client file arrived in the wrong format, a teammate was out sick on a deadline, a login stopped working an hour before a presentation. Each time, I stood there deciding from scratch what to do, and each time the decision cost me more time than the problem itself. A senior colleague noticed and gave me a piece of advice that sounded almost embarrassingly small: write if-then plans for the things that keep happening.
This is the story of how that habit shaped my early career, and how you can use it to build skills faster, whatever field you are entering.
The afternoon that started it
It was a Thursday. A report was due at five, and at three o’clock the data export came back with missing columns. I panicked, rewrote half of it by hand, and delivered late. Afterwards my colleague asked a quiet question: “What did you decide at three o’clock that you could have decided last week?”
Nothing, as it turned out, had been unforeseeable. Exports had failed before. What I lacked was a rule. We sat down and wrote one on an index card: if the export is incomplete, then re-run it once, and if it is still wrong, then message the data owner with the screenshot and start the report skeleton anyway. Two steps, and no judgment call required.
What an early-career if-then plan looks like
The trick is to keep each plan humble. Mine were never grand. They were things like these:
- If a task will take longer than I estimated, then I tell my lead the same day, with a new estimate.
- If I am stuck for more than a short stretch, then I write down what I tried and ask for help.
- If an email thread turns tense, then I move it to a short call.
- If I finish early, then I pick the next item from my learning list.
Notice that none of these require talent. They remove hesitation, and hesitation is what makes junior staff look unsure even when they are capable.
Turning rules into skills
Here is the surprising part. Each rule slowly taught me the underlying skill. The rule about asking for help forced me to describe my problem clearly, and clear problem description is half of what a senior person does all day. The rule about late estimates made me better at estimating. Over months, the card in my notebook turned into judgment I no longer needed to look up.
Digital work in particular rewards this approach. When I moved into more technical projects, the structured thinking in a piece like the onboarding path laid out for new digital-services clients helped me see how projects are broken into stages, and each stage suggested its own triggers: if the brief is unclear at kickoff, then request a written summary; if scope grows mid-stream, then log it and raise it before proceeding.
Building a skills ladder with if-then rules
Careers are partly about collecting abilities in the right order. I started keeping a skills list and attached a rule to each item. For a web skill I wanted: if I have an hour free on a Friday, then I work through one small exercise. For presenting: if I am invited to a meeting, then I prepare one sentence I want to contribute. The goal is not heroic discipline; it is making progress hitch itself to events that already happen.
The cloud and infrastructure side of the business was intimidating at first. Reading about integrating web solutions, cloud infrastructure and AI gave me vocabulary, and the vocabulary gave me triggers. If I hear a term I do not know in a meeting, then I jot it down and look it up that evening. After a year, that single rule had taught me more than any course.
Where I went wrong
I should be honest about the failures. My first draft of a rule list ran to three pages, and I used none of it. Rules that tried to cover every possibility ended up covering none. Another mistake: rules without a clear trigger, like “be more proactive”. My colleague gently crossed those out. “When, exactly?” she asked, and I had no answer.
The fix was to prune. I kept only the rules that had fired in the previous month and wrote each in one short line. The list shrank to a page, and I actually used it.
Skills beyond the desk
Early in a career, travel for work or study often shows up unexpectedly. A client visit in another city, a conference abroad, a training course held far from home. Those trips add their own small crises: a missed connection, a dead phone, a booking that vanishes. I learned to write travel rules the same way as work rules.
One of mine concerned staying connected. If I land in a new country, then I need data on my phone for maps and messages without hunting for a shop. Browsing a travel resource for weighing SIM against eSIM became part of my pre-trip routine, since its country and plan sections and guides helped me think through the question before I flew. The matching rule was simple: if I cannot get a signal on arrival, then I use the saved offline directions to reach the hotel.
Starting your own list this week
You do not need a notebook ceremony. Start a note on your phone with the heading “If, then”. Over the next few days, each time something annoys you twice, add a line. Aim for specific wording: name the trigger, the action and, when it involves a colleague, the role who should hear about it.
- Collect annoyances for a few days.
- Choose the three that cost the most time.
- Write one rule for each, in a single sentence.
- Review the list at the end of the week and edit.
- Share one rule with a colleague and ask whether it sounds sensible.
That last step matters. Sharing a rule exposes hidden assumptions, and often the person you ask has a better trigger than yours.
What changed for me
After a year, the difference was visible to others. I was calmer in meetings because I was not improvising. I asked for help earlier and with more precise questions. Deadlines still slipped now and then, but when they did, I already knew my first move. My manager remarked that I seemed to have grown into the role, but the truth is I had simply moved my decisions to an earlier, quieter moment.
Careers are long, and the people who thrive are often not the cleverest but the ones who waste the least energy on avoidable panic. If-then plans will not make you brilliant. They will, however, give your abilities room to show up, and that is a very good trade for a few lines on an index card.

