Wanting to be better at "communication" or "leadership" is like wanting to be fitter: the goal is real and far too large to act on. This plan shrinks it. You pick one of six competencies, practise one small, watchable behavior each week for four weeks, keep a paper record, and then re-rate yourself. It makes no promise about where you end up. What it gives you is thirty days of evidence about how you actually work.
Why one competency and why four weeks
Spreading effort across all six usually means doing none of them. One competency gives you a single thing to notice and a single page to write on. Four weeks is long enough to repeat a behavior many times and short enough that you still remember why you started.
In this plan a competency is a pattern of behavior, not a talent. The Competency Test from JobCannon rates how often you say you act in six such patterns. It does not measure ability and it is not validated, so nothing here assumes the level word on your result is a fact about you. It is a place to start looking.
Pick the competency that costs you something in your current work: the one you keep wishing were different by Thursday afternoon. That is not necessarily the one with the lowest score.
The four-week ladder
- Week 1: notice. Do the first micro-habit from the list below at every natural chance. Change nothing else.
- Week 2: add the second behavior. Keep week 1 if it comes naturally, but only track the new one.
- Week 3: add the third. If you miss most of the week, repeat it. The calendar is a guide, not a deadline.
- Week 4: add the fourth, and ask one colleague you trust to tell you what they have noticed about this competency in the last month.
Each behavior is small on purpose. It should take seconds, not hours, and another person should be able to see it happen. "Be a better communicator" is not a behavior. "Say the next step aloud before leaving the meeting" is.
Micro-habits for each competency
Four behaviors per competency, one for each week. Choose the set for the competency you picked and ignore the rest.
- Communication. Week 1: before leaving a meeting, say aloud what you understood the next step to be. Week 2: after a conversation, post a one-line summary of decision, owner and date. Week 3: put the request in the first line of any longer message. Week 4: ask one person what was unclear in something you said.
- Problem solving. Week 1: write the problem in one sentence before starting. Week 2: list two possible causes besides the first one you thought of. Week 3: test the cheapest cause first and write down what you found. Week 4: after solving it, write two lines on the cause and what you would check first next time.
- Leadership. Week 1: at the start of a group task, ask who is doing what by when, and propose it if nobody answers. Week 2: once per meeting, propose a decision instead of only asking for opinions. Week 3: give one person specific, kind feedback on something they did. Week 4: hand a piece of work to someone with the outcome stated and the method left to them.
- Planning. Week 1: each morning, write down the three things that must happen today. Week 2: for one deliverable, write dated steps backwards from its deadline. Week 3: add a buffer slot before every date someone else depends on. Week 4: on Friday, compare the plan with what happened and write one sentence on the gap.
- Adaptability. Week 1: when plans change, ask "what changed and what stays the same?" before responding. Week 2: do one routine task a different way on purpose, such as a new tool, route or meeting format. Week 3: when a change lands, tell affected people what it means for them the same day. Week 4: ask for one piece of unfamiliar work and note what you learned.
- Teamwork. Week 1: check in with one colleague each day about what would help them. Week 2: credit a person by name, in writing, for something they did. Week 3: ask for help once on something you would normally do alone. Week 4: when you disagree, say what you agree with first and then name the difference.
Tracking it on paper
You need one sheet per week and a pen. Write that week's behavior at the top, draw seven small boxes, and mark a box when you did it. Next to the box write a few words: where, with whom, what happened. Paper has no notifications to dismiss and nothing to set up.
- Mark only what happened. A missed day stays blank. Do not fill it in on Sunday.
- Write the situation, not your feelings about it: "Tuesday stand-up, said the next step aloud, nobody corrected me."
- Once a week, add one line about what got in the way.
- Keep every sheet. Four of them are the record you will use at the end.
Re-rating yourself after 30 days
On day thirty or thirty-one, retake the Competency Test. Before you look at the new levels, read your own sheets and write one sentence on what changed in what you do.
Then expect some noise. A self-rating moves with your mood, how the week went and which examples happen to come to mind as you read each statement. A small shift up or down on one competency is not a verdict either way. The pattern in your sheets is better evidence: did the behavior happen on most days, did it get easier, did anyone react to it?
A higher result is nice, but check it against the sheets before believing it. A lower one is not necessarily a setback either: looking closely at your habits can make you rate yourself more strictly, so sharper eyes can produce a lower number. And if nothing moved, you still know more than you did, because you have a month of records instead of an impression.
This plan is practice, not a promise. It will not fix a role that makes a behavior impossible, and it does not replace feedback from people who see your work. Whatever the month shows, keep the sheets: they hold the real examples you need for a strengths-and-weaknesses answer and for the bullets in showing competencies on a resume and in reviews. For the wider question of how far to trust any self-rating, read how accurate self-assessment at work really is and how to self-assess your skill level honestly. For what you can do rather than how you work, the Skills Audit is the companion.