How to learn an unfamiliar industry in first 90 days as a product manager on Mac

What ramping up on a new domain costs you

The cost shows up in small places first. You nod through a planning meeting when you do not follow an acronym. You ask a question a colleague answered last month. You write a spec that reads well but misses how customers buy. Gallup's research covers general onboarding, not product managers, so read its numbers as a rough guide.

The bigger cost is people and time. Gallup says organizations often lose one-third to two-thirds of new hires within their first 12 months. It also says replacing one employee can cost one-half to two times the annual salary, and calls that a conservative estimate. Your own cost is smaller, but it compounds. Each slow month pushes your first real decision further out.

Why a new industry slows you down longer than expected

Most of the slowdown comes from knowledge nobody wrote down. Some of it sits in a few people's heads. Some of it sits in old tickets and signed contracts. The rest sits in the way a sales team talks about a deal.

Research on newcomers points the same way. Bauer and colleagues reviewed 70 newcomer samples in a 2007 meta-analysis. The authors say their results generally supported a model in which information seeking and socialization tactics lead to role clarity and self-efficacy. In plain terms, the model suggests that people who ask and get answers feel less lost, sooner.

That study looked at people who joined organizations, not people moving into a new domain inside a job. Treat it as a direction, not a promise.

Four gaps that slow new product managers down

• Vocabulary gap: the same word means something different in each company, and sometimes in each team.
• Customer gap: you know the product but not the buying process, the budget owner, or the daily workflow.
• Rule gap: contracts, compliance, and data limits decide what you can build, and they rarely appear in a pitch deck.
• Trust gap: engineers and sales leaders check whether you understand their world before they share hard news.

A worked example: moving from consumer apps to warehouse software

Say your last product was a consumer app, and your new one sells software to warehouses. In week one, the word order means a customer purchase to you. On the warehouse floor, it may mean a picking task with a deadline. Your analytics dashboard shows orders per day. The operations lead talks about dock time. Neither of you is wrong. You simply hold two vocabularies.

The fix is not to read a glossary cover to cover. Pick the terms that appear in your next few meetings. Write each one as a sentence you could say to a new hire. Then ask the operations lead to correct it, because the correction comes from the person who does the work.

Each correction becomes a card or a note. When the same word shows up again, check your notes before you assume it means what it meant last time.

A 90 day plan that fits around your normal work

Spread the work out. Short, regular sessions beat one long catch-up day. Cepeda and colleagues reviewed distributed practice in a 2006 review that covered many experiments. They found that the best gap between study sessions grows as the retention interval grows. For you, that means revisiting a term after a few days, then after a few weeks, instead of cramming it once.

Those studies used lab memory tasks, so treat the schedule as a starting point for work knowledge, not a law.

Set up a glossary you can test yourself on

Use any note app you already have, or paper. The format matters less than the habit. The setup below works in Notion, in Obsidian, or in a notebook.

1. Create a table with these columns: Term, Plain meaning, Who says it, Example, and Confidence. In Notion, type / and choose a database option.
2. Write each meaning in your own words, then add one example from a real ticket, call, or report.
3. Mark Confidence low for anything you cannot explain without looking. Review those rows first.
4. Copy the terms you keep missing into an Anki deck, one card per term. Create the deck from the main window.
5. In Deck Options, check the FSRS setting. FSRS can only be enabled globally, not per preset.
6. Leave desired retention near the default. Anki's manual says workload rises quickly above 90%, and may overwhelm you above 97%.

Practice testing is the habit that matters most. Dunlosky's review rated practice testing and distributed practice among the most effective learning strategies. It rated rereading and highlighting as less useful. Close the doc, write the definition from memory, then check it.

Dunlosky also notes that even the best strategies only work when you use them and stay motivated. Attach the habit to a time you already keep, like the quiet minutes after lunch.

Mistakes people make in their first 90 days

• Reading the whole wiki before talking to anyone. Start with the words you hear in meetings, then go deeper.
• Asking for a crash course in front of the team. Book a short one on one instead.
• Learning the slide deck vocabulary and missing the customer's words. Slides are often written for executives, not for the people doing the work.
• Pasting client, patient, or financial records into any tool for a quick answer. Follow your employer's rules first, every time.
• Waiting until the end of the quarter to share a first opinion. Share small early readings and ask whether you read them right.

Regulated and confidential work needs stricter limits

Some domains carry rules about who can see data. Healthcare, law, and accounting are common examples. If you work with patient, client, or financial records, follow your employer's rules on that data before you use any tool. That includes dictation, screenshots, and chat. Your employer's policy decides, not this page.

Lazur sees your screen only while you hold the shortcut. Audio and the screenshot go to AI providers to answer, and they are not stored. Content is never used to train AI models. Those are Lazur's stated terms, not a legal review, so check them against your own policy.

Where Lazur fits into the learning routine

Lazur helps most with questions that come up in the middle of work. Hold ⌥ ⌘ to ask about anything on screen, and Lazur answers out loud. Ask where a control lives, and Lazur draws a circle and a label around it. Hold fn to dictate a definition at the cursor in any app.

Research is the other use. Lazur runs research in its own Chrome tabs and returns a summary and a report. That helps when you want a quick scan of how public sources describe a term or a regulation. Check the sources it cites. A summary is a starting point, not a verdict.

Lazur does not click buttons or edit files for you. It guides you one click at a time and waits for each click. For a glossary, you still write the definitions. Lazur helps you find the field, read a term back to you, and keep odd industry words spelled right through your personal dictionary. You can download Lazur or compare plans on the pricing page.

Checkpoints for the first 90 days

A plan needs checkpoints, or it becomes a list you never reopen. At each checkpoint, test yourself without notes. Can you explain the buying process in plain words? Can you name who approves budget and who uses the product? Can you spot when two teams use one word in different ways?

• Explain the customer's buying process in a few plain sentences, with no notes.
• Name the person who approves budget, and the person who uses the product every day.
• Name the rules that limit what your team can build, and where each rule is written down.
• Describe one term that means different things to two teams, and which meaning your roadmap uses.

Next steps you can start today

Pick one meeting this week. Write down every word you did not fully follow. Put them in one note, then take the most common ones to a colleague who works in the domain.

Then start the plan. Create the note, add the first few terms, and set a short quiz for tomorrow morning. A small start on the first day beats a perfect plan that never begins.