Professional guides

Guide 01

Interview preparation

An interview is a structured conversation with an unusual constraint: both sides are trying to predict future behaviour from a short sample of speech. Understanding that constraint explains most of what makes preparation effective. Panels are not looking for the most polished speaker. They are looking for evidence — specific, recent, verifiable — that you have done something close to this before, and that you will be straightforward to work with.

Research that changes your answers

Generic research produces generic answers. Read the job posting twice and highlight the verbs, because verbs describe the work while adjectives describe the aspiration. Then find three concrete things: what the organisation has recently changed, what constraint it is operating under, and who you would work with most closely. Public annual reports, news coverage, and the professional profiles of the team are usually enough. A single well-placed observation about the organisation's actual situation does more than a paragraph of praise.

Building a story bank

Rather than preparing answers to predicted questions, prepare eight to ten stories from your working life and learn to point them at whatever is asked. Good candidates: a time you fixed something broken, a time you disagreed with a decision, a time you missed something, a time you had to learn quickly, a time you worked with someone difficult, a time you influenced without authority.

Structure each one the same way: the situation and why it was hard, what you specifically did, what happened as a result, and what you would do differently now. That final element is the one most candidates omit, and it is often the most persuasive part, because it demonstrates the reflective habit that makes someone improve in a role.

Keep each story to about ninety seconds spoken. Time yourself once; almost everyone runs long, and a story that outstays its usefulness costs you the goodwill that the content earned.

Handling the hard questions

Questions about a gap, a dismissal, a short tenure or a career change are asked to see whether you are defensive, not to catch you out. Answer briefly, factually, without blame, and turn quickly to what you learned or what you are doing now. Two sentences of explanation and one of forward direction is usually the right shape. Long explanations signal that you consider it a serious problem, and panels take that cue.

When you do not know something technical, say so plainly and describe how you would find out. Every experienced interviewer has seen bluffing, and it costs far more than the gap it tried to hide.

Your questions for them

Ask about the work, not the perks. Useful questions: what does a good first six months look like; what is the hardest part of this role that is not on the posting; how does the team decide when something is finished; what would you want changed about how this role currently operates. These get you real information for your own decision, which is the point — an interview is also your assessment of them.

Afterwards

Send a short note within a day: thank them, reference one specific thing discussed, and restate your interest in one sentence. Then write your own debrief while it is fresh — which questions caught you unprepared, which stories landed, what you would answer differently. That debrief is the reason your fourth interview will be substantially better than your first.

Guide 02

Professional communication

Communication at work is largely a series of small routing decisions: what to say, to whom, in which channel, at what level of detail. Errors in routing cause more friction than errors in wording, and they are easier to fix.

Choosing the channel

Each channel has a shape it suits. Writing is for anything that must be found again: decisions, requests with deadlines, records of agreement, and detail people need to consult. Conversation is for anything with emotional content, disagreement, or ambiguity that would take four written exchanges to resolve. Chat is for the short-lived and the low-stakes; anything that matters should leave chat and land somewhere retrievable.

A reliable rule: if a message has taken you more than two attempts to word carefully, it is probably a conversation. If a conversation has repeated itself twice, it probably needs a written summary.

Tone that travels

Written tone is read more harshly than it is written, especially when the reader is busy or already worried. Three adjustments cover most of it: use complete sentences with a greeting for anything sensitive, remove intensifiers that read as pressure, and state your intent explicitly when it might be misread — “asking so I can plan, not chasing” costs four words and prevents an entire misunderstanding.

Avoid apologising as a default opening. “Sorry to bother you” frames the request as an imposition before the reader has judged it. “Quick question about Thursday's report” is friendlier and more useful.

Matching detail to the reader

The most common failure in professional communication is a single message written at one depth for an audience reading at three. The practical answer is layering: conclusion first, then a short body for the interested, then detail in an appendix, attachment or link. Nobody has to read past their own need, and nobody has to ask for what is missing.

Disagreement and escalation

Disagree in the smallest room that includes everyone affected. Put the disagreement in terms of the shared objective — “I think this timeline risks the launch quality we agreed on” — rather than in terms of position. If a decision goes against you and it is not a matter of safety, ethics or legality, commit visibly and stop relitigating it. Public reluctance after a decision costs credibility that the original argument did not.

When escalation is genuinely necessary, tell the person first. Escalating without warning turns a disagreement into a breach of trust, and the second problem outlasts the first by years.

Guide 03

Meeting management

Meetings are the most expensive recurring instrument in most organisations and the least often examined. A weekly hour with eight people costs roughly a full working month per year. That does not make meetings wasteful — some work genuinely requires people in a room — but it does justify treating them with more care than a calendar invitation usually receives.

Before: the invitation is the design

Three lines in the invitation change everything that follows: the outcome, the owner, and what attendees should do to prepare. “Decide the launch date; owner: Priya; please read the two-page brief attached” produces an entirely different room from “Launch discussion”. People prepare for decisions and drift through discussions.

Invite the smallest group that can make the decision. Everyone else can receive the notes. Attendance is not a courtesy; it is a claim on someone's working hours, and treating it as optional information rather than obligation is a kindness that costs you nothing.

During: structure carries the room

• Start on time, even at the cost of repeating context later. Waiting punishes punctuality and teaches the room to arrive late.
• State the outcome first, aloud, even though it is written in the invitation.
• Take input before opinion. Ask the people closest to the work to speak before the most senior person does; once a senior view is stated, the range of opinions in the room narrows sharply.
• Park what is out of scope, visibly, in a list. Parking is not dismissal, and saying so keeps the room cooperative.
• Close with actions read aloud: what, who, by when. If that takes more than two minutes, the meeting was too broad.

After: the record

Notes should be short and should privilege decisions over discussion. Six months later, nobody needs the argument; they need to know what was decided, by whom, and what was explicitly ruled out. Send within a day, while people can still correct you cheaply.

Meetings that should not exist

A recurring meeting deserves an annual test: what decision does this produce, and what would happen if it were cancelled for a month? Status-only meetings are usually a written update in disguise. Meetings with no outcome and eleven attendees are usually a governance ritual, which may be legitimate — but should be named as such rather than defended as productive.

Chairing well is a learnable skill and a visible one. It is one of the few professional behaviours observed directly by people senior to you, which makes it disproportionately worth practising.

Guide 04

Career planning

Career planning has a reputation problem. It sounds like predicting a decade, and nobody can do that. A more useful definition: knowing what you are optimising for right now, testing it against reality regularly, and keeping enough optionality that a change of mind is not catastrophic.

Direction before destination

Job titles are poor planning units. They vary between organisations, they change, and they describe status rather than daily activity. Better units are the things that actually determine satisfaction: the kind of problem you work on, the amount of autonomy, how much of the day is spent with people, the pace, the geography, and what you are learning.

Write your current preference across those six dimensions. It will change, and that is the point — a written preference from two years ago is the only way to notice that it has.

The three-part review

Twice a year, spend an hour on three questions. What did I get better at, with evidence? What did I do that I would not want to do for another five years? What did I see someone else doing that I envied? The third question is the most informative and the least asked; envy is an unreliable moral guide and a fairly reliable signal of direction.

Making the next move visible

Most opportunities are allocated to people whose recent work is known, not to those whose potential is theoretically greatest. This is not office politics; it is how decisions get made under uncertainty. The remedy is unglamorous and effective: keep a record of what you delivered and what changed because of it, make sure your manager knows what you want next, and make sure at least two people outside your immediate team can describe your work accurately.

Progression is not only upward

The assumption that advancement means management costs many people several years. Depth, breadth and management are three different directions, and only one of them involves spending most of your day on other people's work. Try the work before accepting the title — run a project, mentor a colleague, cover a lead's absence — and treat “I tried it and prefer the craft” as a legitimate and permanent answer.

When to stay and when to move

Two questions cover most cases. Am I still learning something I value at a rate I am satisfied with? And can the thing I want next plausibly happen here within twelve months? Two clear noes generally mean it is time to look, without drama and without burning anything down. One no usually means it is time for a specific conversation rather than a search.

Guide 05

Networking

Networking has an unpleasant reputation because the most visible version of it is transactional: contact collected, favour requested, relationship abandoned. That version works poorly and feels worse. The alternative is slower and considerably more effective — building a small number of real professional relationships and being useful in them over time.

Start with people you already know

Most useful professional connections are dormant rather than absent: former colleagues, classmates, people from a previous team. Reconnecting is easier than meeting, and it carries context that a new contact cannot have. A short, specific message — what you are doing now, one thing you remember working on together, and one genuine question — is almost always welcome.

Informational conversations

The most reliable networking instrument is a twenty-minute conversation with someone doing work you are curious about. Ask for twenty minutes, say why you asked them specifically, and come with two or three questions you could not answer from public sources. Do not ask for a job in a first conversation; it converts a pleasant exchange into an awkward one and reduces the chance that they think of you later.

Good questions: what does the ordinary week look like, what surprised you about this work, what would you want someone entering it to know, and who else should I be talking to. That last one is how a network actually compounds.

Being useful

The most durable networks belong to people who are known for being helpful in small, unremarkable ways: sending a relevant article, making an introduction, answering a question properly, remembering that someone was preparing for something and asking how it went. None of this is strategic in the moment, which is exactly why it works.

Following up

Write down what you learned and one detail about the person, then follow up once with the outcome of their advice. “You suggested I talk to the operations team before applying — I did, and it changed what I asked for. Thank you.” This one message does more for a relationship than a year of quiet connection, because it demonstrates that their time produced something.

For people who find this difficult

If large events are draining, skip them. One-to-one conversations, written correspondence, small special-interest groups and volunteering all build professional relationships more effectively for most people than a room of two hundred. Networking is not a personality type; it is a set of habits, and the quiet versions work at least as well.

Guide 06

Workplace etiquette

Etiquette is not formality. It is the set of shared conventions that let people who did not choose each other work together without friction. Most of it is invisible until it is missing, which is why it is so rarely explained and so often the source of avoidable trouble.

Reliability conventions

Arrive on time, or say early that you will not. Reply to messages that need a reply, even if only to say when a real answer will come. Meet the deadline, or renegotiate it before it passes rather than after. These three behaviours account for most of what people mean when they describe a colleague as easy to work with, and none of them require talent.

Shared space and shared time

In an office: keep loud conversations away from concentrating people, clean what you use, and treat a booked room as booked. In video meetings: mute when not speaking, say your name the first few times if the group is unfamiliar, and avoid speaking over someone on a delayed connection — the delay is not their fault, and interruption compounds it.

Respect the hours agreed. Sending a message outside them is generally fine; expecting a response is not. If your own working hours are unusual, say so explicitly, because otherwise a message at nine in the evening reads as an expectation to whoever receives it.

Credit and blame

Attribute ideas to the person who had them, in public, by name. Take responsibility for your own errors early and without ceremony — a short, factual account with what you are doing about it is nearly always received better than an elaborate apology. Correct someone privately unless the error is about to cause harm.

Difference

Canadian workplaces bring together people from many backgrounds, first languages and working cultures. Norms about directness, interruption, humour, hierarchy and small talk vary considerably. Assume good intent, ask rather than infer, and adjust; someone speaking their second or third language in a meeting is doing something demanding, and a small amount of patience is the least expensive courtesy available. If you get a name wrong, ask how it is pronounced, use it correctly afterwards, and do not make it into an occasion.

Boundaries

Etiquette runs in both directions. It is entirely acceptable to decline optional social events, to keep personal matters personal, to say you are at capacity, and to expect to be treated respectfully. Politeness is not deference, and the conventions above are meant to make work easier for everyone in the room — including you.