Topic 9 — Tools of the trade

Goal: Recognize the tools project managers use to plan, track, and communicate.

Lesson 9.1 — The tools don't make the project manager

On Renata's third day at Cartwheel, the engineering director, Tomás, drops a sentence that nearly stops her heart: "You'll be running everything in Jira — you've used it, right?" She hasn't. Her whole career, she ran 300-person conferences and ten-table weddings out of a shared spreadsheet, a wall of sticky notes, and a phone that never stopped buzzing. She nods, panics quietly, and spends that evening bracing to be found out.

She needn't have. By Friday she's moving cards around a Jira board like she's done it for years, because the thing she was actually good at — knowing who owes what by when, and chasing it warmly — had nothing to do with the software.

That's the first thing to settle, because it's the thing new project managers get backwards. Tools support the craft; they aren't the craft. What makes someone good at this job is organization, clear communication, and people skills. The tool is just where those skills get written down. A disorganized person with Jira is still disorganized. Renata, organized to her bones, was productive in a tool she'd never opened within two days.

So why learn the tools at all? Two honest reasons. First, knowing the names kills the first-week anxiety Renata felt — you walk in already speaking the language. Second, job ads list them, and interviewers ask. "Familiar with Jira" appears in a huge share of project-manager postings, and you want to answer that without flinching.

Learn the category each tool serves, not its feature list. Features change every release; categories last a career.

There are maybe five categories total. Once you can name them and say which tool lives in each, you sound fluent, and you are, because the coordinating you'll do inside them is the work you already understand.

Lesson 9.2 — Work tracking: the core category (and why it's usually Jira)

Picture the one screen Renata stares at most of the day. It's a board: columns labeled To Do, In Progress, In Review, Done, and cards she drags left to right as the squad's driver-app features move along. Every task lives there, every assignee, every status. When Tomás asks "where are we?", the answer is on that board.

This is the work-tracking (or task-tracking) category, and it's the heart of the toolkit. If you learn one category cold, learn this one.

In tech, the default tool here is Jira. It's the most common work tracker in software teams, and it's built tightly around Scrum and Kanban — the very methods from Topics 5, 6, and 8. Jira speaks in issues (its word for any task, bug, or story), organizes them into boards and sprints, and generates the reports stakeholders love. That tight fit with Agile is exactly why it dominates tech, and why "comfort with Jira" shows up in so many job ads.

Jira isn't the only one, and it isn't even the friendliest. The popular alternatives are worth knowing by name:

• Trello — the gentlest on-ramp; a Kanban board you can set up in two minutes. Great for small or simple work, gets cramped for complex projects.
• Asana — broad work-management used widely beyond engineering; strong for connecting daily tasks to bigger goals.
• Monday.com — colorful and approachable, popular with smaller teams and non-engineering work.
• Linear — the fast, keyboard-driven modern challenger to Jira, loved by developer-heavy teams.

You do not need to master all five. Get comfortable in one — ideally Jira, since it's the most transferable in tech — and the others feel like dialects of the same language. Marcus, Renata's tech lead, has used three of them across past jobs and barely notices the switch anymore: a card is a card, a column is a column.

A nuance that trips people up: planning and scheduling (timelines and task dependencies) often live in the same tool. Most of these trackers include a Gantt chart view (the timeline bars from Topic 3) so you can see what depends on what and when it all lands. For heavier, detailed schedules, some teams reach for Microsoft Project, and plenty of smaller teams just use a spreadsheet. Scheduling is frequently a view inside the tracker you already have open rather than a separate app.

Lesson 9.3 — Where the words live: docs and communication

Renata runs a sprint retro and the team makes three real decisions — postpone the offline-maps feature, add a QA gate before release, ask Priya to re-rank the backlog. If those decisions live only in people's memories, they evaporate by Tuesday.

So she writes them down. That's the documentation and collaboration category: the place project plans, meeting notes, decisions, and summaries are kept so the whole team can find them later. The common tools are Confluence (Atlassian's wiki, the natural partner to Jira), Notion (an all-in-one workspace many startups like), and plain Google Docs. Cartwheel keeps its project plans and retro notes in Notion; the choice matters far less than the habit of writing things down somewhere shared.

Separate from where words are stored is where words are spoken in real time — the communication category. This splits cleanly in two:

• Chat, for the all-day back-and-forth: Slack or Microsoft Teams. This is where Renata pings Jamie "are you blocked on the API key?" and gets an answer in thirty seconds.
• Calls and video, for standups, planning, and remote face time: Zoom or Google Meet.

Don't overthink which is which. The useful distinction is persistent docs you'll re-read (Confluence, Notion, Docs) versus live conversation (Slack, Teams, Zoom, Meet). A decision made in a Slack thread or a Zoom call that never makes it into the docs is a decision you'll re-litigate in a month — so a sharp project manager moves the important bits from the chatter into the record.

Lesson 9.4 — The quiet workhorse: spreadsheets

Here's the tool nobody puts on a résumé and everybody uses every single day.

When Renata needs to track the driver-app budget, sketch a rough three-week schedule before it's worth setting up in Jira, or keep a running list of project risks, she doesn't open anything fancy. She opens a spreadsheet — Excel or Google Sheets.

Spreadsheets are the project manager's quiet workhorse, and they're everywhere because they bend to any shape you need:

• Task lists when the work is too small or too early to justify a full tracker.
• Budgets, summed and tracked with a few formulas.
• Simple schedules, a column of dates and owners.
• A RAID register — the running log of Risks, Assumptions, Issues, and Dependencies that a project manager keeps a close eye on (you'll meet RAID in the risk topic).
• Quick reports for a stakeholder who just wants the numbers.

The reassuring part, especially if spreadsheets intimidate you: the basics carry you a long way. Typing in cells, a few formulas like SUM, sorting and filtering, color-coding a status column is most of what the job asks, and you can learn it in an afternoon. Renata ran entire weddings on Google Sheets; the muscle transferred straight across.

If you're unsure where to track something and don't have the right tool yet, a spreadsheet is almost never the wrong answer to start.

Lesson 9.5 — Dashboards, and the balance to strike

Tomás, the sponsor, doesn't want to read a paragraph from Renata every morning. He wants to glance at a screen and know whether the driver app is on track. That glance is what dashboards and reporting are for.

Most of the tools above generate these automatically. Jira can produce a burndown chart — the line that shows how much sprint work remains versus how much should remain (from Topic 5) — and a project dashboard can show RAG status, the red / amber / green health signals that let a stakeholder read a project's state in one second flat. The point of a dashboard is self-service: instead of Renata hand-writing a status update, Tomás pulls up the board and sees it himself, live.

Which brings us to the attitude to carry into any job. Be tool-aware, not tool-obsessed.

The trap is believing the tool is the skill — that you must master every Jira setting before you're "ready," or that switching companies means starting over. Neither is true. A project manager with strong organization and people skills picks up any company's specific stack in days, the way Renata picked up Jira in two. Walk in knowing the categories — a task tracker (Jira), docs (Confluence or Notion), comms (Slack), and the trusty spreadsheet — and you'll be productive fast. The tools change between companies; the craft of organizing people and work travels with you everywhere.

Worked example — Renata's first week, mapped to the toolkit

Renata joins Cartwheel on Monday, terrified of a tool list. By Friday she's used the whole map without trying to.

Monday. Priya, the Product Owner, walks her through the Jira board for the driver app — To Do, In Progress, In Review, Done. Renata drags two cards and the panic recedes; this is just a smarter version of her sticky-note wall. Work tracking.

Tuesday. Marcus gives build estimates in a planning call over Zoom, and the squad chats all afternoon in Slack about an API hiccup. Communication. Renata notices the standup runs remote, so Zoom is the squad's daily face-to-face.

Wednesday. She writes the sprint plan and the team's working agreements in Notion so nobody has to remember them. Docs. A decision from yesterday's Slack thread — defer offline maps — she copies into the Notion record so it stops being a rumor.

Thursday. The budget needs tracking and there's no tool for it, so she builds a quick Google Sheet with a SUM at the bottom and starts a tab for the RAID log. Spreadsheets.

Friday. Tomás asks for status. Instead of writing him an essay, Renata points him at the Jira burndown chart and a simple RAG dashboard — green on scope, amber on the integration. Dashboards. He reads the project's health in one glance and lets her get back to work.

Five categories, one week, zero memorized feature lists. She was fluent because she already knew the craft — the tools just gave it somewhere to live.