Learn any tool

The tool will change. The way you learn it won't.

Tools change every year, new CRM, new AI copilot, new dashboard nobody trained you on. Clients don't care which tools you already know. They care whether you can pick up the one they use, fast, without hand-holding. This page does not teach you software. It teaches the method for learning any software, so the next unfamiliar tool is a weekend, not a wall.

The tool you learn today will be replaced. The way you learn tools will not. Master the method and every new tool is a weekend, not a course.

Last verified · Jul 2026

The 5-step method

How to learn any tool, fast

Run these five steps on the next unfamiliar tool a client hands you. Same five steps, every time, regardless of what the tool is.

01

Define the outcome

Not "learn Notion." Instead: "build a client-ready project tracker in Notion, from a blank workspace, with no template." A topic never ends. An outcome tells you exactly when you're done.

Do this: Write one sentence naming the real job you need to do, the deliverable, not the tool's name.

02

Find the 20%

Every tool has a fat manual and a thin daily reality. Most of what's in the docs, you'll touch once a year or never. Real job posts and real workflows show you which functions get used, ignore the rest for now.

Do this: Read 3 real job posts or workflow guides for the role. List the 5–8 functions they mention.

03

Build a real artifact in the first hour

Skip the six-hour course. Watch twenty minutes of the fastest reference you can find, then build something real, and probably broken. A broken artifact tells you exactly what you don't know yet. A video never does.

Do this: Set a 60-minute timer. Produce one finished, if rough, thing: a sheet, an automation, a dashboard. Stop when the timer stops.

04

Get feedback that stings

Comfortable feedback, "looks great!", teaches nothing. Ask a real person to be blunt, or paste your work into AI and ask it to critique against the rules of the job: the gaps, the missed edge case, what a client would reject.

Do this: Ask directly: "What's wrong with this? Be specific and unkind." Fix the top three things it names.

05

Teach it back

Explaining something out loud, to a beginner, or in a one-page SOP, is the fastest way to find the parts you only half-understand. If you stumble explaining a step, that's the part you haven't learned yet.

Do this: Write a one-page SOP for the artifact you built, as if training someone else to redo it tomorrow.

The reusable instrument

The tool teardown

Run this on any tool before you open a single tutorial. Six questions, answered in writing, in about fifteen minutes. It works because every tool, no matter how unfamiliar, is really just a set of nouns (the things it manages) and verbs (what you do to them). Learn those and you've learned the tool.

Run this on any tool before the tutorial

01

What job does this tool exist to do?

One sentence. A CRM exists to track who might buy and who already did. If you can't name the job in a sentence, you haven't found it yet.

02

What are its core objects, the nouns?

Sheets = cells, ranges, formulas. A CRM = contacts, deals, pipelines. A design tool = frames, layers, components. Name the 3–5 things everything else is built from.

03

What are the 5 actions I'll do daily, the verbs?

Create, filter, assign, send, report, whatever they are for this tool. Master these five before you touch anything else in the menu.

04

How do I import and export?

Never get locked in. If you can't get your data out in an open format, CSV, PDF, an API, you don't own your work. The vendor does.

05

What breaks, and how do I undo it?

Find the undo, the version history, the trash, before you need them. Break something on purpose in a test file so the first real mistake isn't the scary one.

06

Where are its real docs?

The vendor's own help center or docs site, not a second-hand summary. Bookmark it before you need it at 11pm.

Learning the nouns and verbs of a tool is how you learn it in hours instead of weeks.

Spend your hours well

Is it even worth learning?

Not every tool deserves front-loading. Run any candidate through these four questions before you sink an hour into it.

Is it in real job posts?

Search 10 live listings in your niche. If a tool doesn't show up in any of them, don't front-load it, learn it on demand if a client ever asks.

No-cost tier or recognized certification?

If you can't touch it without a company card, it's a bad first tool. Vendors that want adoption make the entry point no-cost, see below.

Is the skill transferable?

"I can build a pivot table" moves with you between five spreadsheet tools. "I know which exact button to click" doesn't. Learn the transferable version.

Who owns the data?

If the tool disappeared tomorrow, could you export everything and rebuild elsewhere? If not, you're renting your own work.

Practice targets, not a curriculum

The tools the market asks for

These are not a list to passively work through. They're what real job posts ask for, pick one, run the teardown on it, hit the 60-minute build. The tool is the gym, not the goal.

  • Coreasked for in most job posts in the lane; learn first
  • Intermediateasked for in some posts; learn when a role needs it
  • Advancedspecialist roles; learn on a client's request
Worked examples, not a library

Codes for efficiency

The snippets below aren't a library to paste blindly, they're worked examples. Study one closely and you can write your own for any spreadsheet or inbox task you have.

What triggers it?

An edit, a click, a schedule. Apps Script's onEdit(e) fires on every cell change; a formula fires on every recalculation. Know the trigger before you trust the output.

What does it read?

Which cell, range, or field does it pull from? Trace every reference before you run it on something that matters.

What does it change?

Which cell does it write to, and could it silently overwrite something you needed? Test on a copy first, always.

What happens with different data?

A blank cell, an extra column, a renamed sheet. Try it broken on purpose in a test file before a client's real data does it for you.

Sheets: auto-timestamp on edit

Apps Script
function onEdit(e){
  const s = e.source.getActiveSheet();
  const r = e.range;
  s.getRange(r.getRow(), 10).setValue(new Date());
}

Sheets: clean & trim text

Formula
=TRIM(CLEAN(PROPER(A2)))

Gmail: canned follow-up shortcut

Text
Hi [Name], floating this back up, still keen to help with [task]. Any questions I can answer?

Sheets: days until due

Formula
=IF(B2="","",B2-TODAY())
Found by you, not handed to you

Certifications worth earning

Vendors give away certifications on purpose, a certified user is a lifelong user. HubSpot, Google, Meta, Canva, and Notion all fund recognized certification programs to drive adoption. We won't hand you a list that goes stale in a year. Find your own, live, in under five minutes.

01

Search the pattern, not a list

"<tool name> certification" or "<tool name> academy." Every major vendor runs one, and a live search puts today's real link in front of you, not a dead one from an old blog post.

02

Go to the vendor's own domain

hubspot.com/academy, skillshop.withgoogle.com, and so on, never a reseller course pretending to be official. If it isn't on the vendor's own domain, it isn't the no-cost one.

03

Confirm it's no-cost before you start

Some gate the exam behind a trial that wants a card. Read the fine print for ninety seconds before you commit an afternoon to it.

Force a real artifact

Practice drills

Reading the method changes nothing. Running it does. Pick one drill and start today.

The 60-minute build

Pick one tool from the landscape above. In one hour, produce a real, finished-if-rough artifact, a sheet, an automation, a dashboard. No tutorial past minute twenty.

The teardown run

Run the Tool Teardown above on that same tool. Write the six answers down, don't just think them.

The five-minute teach-back

Explain what you built to someone else, or record yourself explaining it, in under five minutes with no notes.

The cold rebuild

A week later, close every tab and rebuild the same artifact from a blank page. Whatever you forgot is what you didn't learn.

One method, every tool

This method isn’t just for tools.

The same five steps work on finding work, deconstructing a deliverable, or getting unstuck. See where else it applies, or go pick a niche to run it on first.