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

> A product manager's plan to learn an unfamiliar industry in 90 days: costs, causes, free fixes, and where Lazur helps on Mac.

URL: https://www.lazur.app/for/product-managers/problems/learn-unfamiliar-industry-first-90-days
Updated: 2026-11-08

To learn an unfamiliar industry in your first 90 days, build a glossary, map the customers and money, then test what you know against real work. Gallup says most people take 12 months or more to get up to speed in most jobs. A plan will not erase that curve, but it shows you where you stand each week.

## Quick answer

- Treat the first 90 days as a learning project with a written plan, not a feeling you hope fades.
- Learn the words, the customers, the money, and the rules, in that order. Each one makes the next one easier.
- Test yourself with spaced practice. Rereading and highlighting feel productive but are rated less useful.
- Lazur can explain a term on screen out loud and run background research. It does not replace talking to customers, and regulated data still follows your employer's rules.

## What ramping up on a new domain costs you

- **Credibility in the first meetings.** Stakeholders listen for domain fluency early, because it shows whether you understand their problems. A wrong term in a planning review can make people hold back their real concerns. That trust is slow to rebuild once it slips.
- **Slower decisions.** Without the rules and money flow, every decision waits for someone to explain them. You bring questions back to the team instead of recommendations. Gallup's panel data says employees who rate onboarding as exceptional are nearly 2 times more likely to feel fully prepared. The sample size was not given.
- **Turnover, both sides.** Gallup says about a third of new employees do not last 90 days. A slow ramp can make a new role feel like a mistake. The company pays for that too, since Gallup estimates replacing one employee can cost one-half to two times the annual salary.
- **Wrong features, built well.** If you misread the customer's workflow, the team builds the wrong thing well. Engineers finish the sprint, and the customer still does not change how they work. You pay for that in rework and in the trust you spent to get the work started.

## Why it happens

1. **Jargon hides in plain sight.** Teams use words without defining them, because everyone in the room already knows what they mean. You hear a term once, nod, and move on. The next meeting assumes you caught it, so small misses stack up across a month.
2. **Knowledge lives in people, not documents.** Sales leads carry the buying process in their heads. Support staff know which bugs make customers angry. The wiki often trails behind, so you learn the real version only by asking the right person.
3. **Most onboarding skips the domain.** Gallup reports that only 12% of employees strongly agree their organization does a great job onboarding new employees. That figure suggests most people do not get strong onboarding. Domain knowledge is the part that rarely gets a plan.
4. **Newcomers who do not ask stay confused.** Bauer's meta-analysis links information seeking and socialization tactics to role clarity and self-efficacy. If you wait to be briefed, you may get less of both. Asking can feel like admitting a gap, so people often delay it.
5. **Reading feels like progress.** Rereading docs and highlighting a slide deck give a sense of learning. Dunlosky's review rated these strategies as less useful than practice testing. The feeling is misleading, so test yourself early and often.
6. **Rules and money are slow to learn.** Vocabulary shows up in every meeting. Contracts, pricing, and compliance limits appear only when a deal or an audit forces them into view. You can miss them for weeks, and a roadmap built without them can need rework.

## How to fix it

- **Write glossary entries with examples.** Write each term in your own words, then add one example from a real ticket, call, or report. Ask someone who works in the domain to correct it. The correction teaches you more than your first draft did.
- **Quiz yourself with spaced practice.** Put each term in an Anki deck and answer from memory before you check. Anki's FSRS scheduler sets review timing from your answers. Keep desired retention at the default unless you know why you want more.
- **Ask one person for a standing slot.** Pick one person in the domain, such as a sales lead or support manager, and ask for a short recurring conversation. Bring the glossary and one question for each term you could not explain. Ask which terms they would never use in front of a customer.
- **Read tickets and call notes.** Search your team's tracker for the customer's words. Read the complaints, not only the feature requests. Copy exact phrases into your glossary, because the customer's vocabulary is what your product will be judged against.
- **Map the money and the rules.** Draw the path from a customer payment to your revenue line, then list each rule that limits the product. Mark which rules are firm and which are preferences. Bring the list to your manager and ask which rules are fixed.
- **Capture words during meetings.** Type the unfamiliar term into a plain notes file while you listen, using a short shorthand like a question mark. Clean up the entry after the meeting. This needs no paid tool, and the notes stay on your own machine.

## 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.

- **12%** of employees strongly agree their organization does a great job onboarding new employees ([source](https://www.gallup.com/workplace/235121/why-onboarding-experience-key-retention.aspx))
- **12+ months** for most people to get up to speed in most jobs, according to Gallup ([source](https://www.gallup.com/workplace/246242/essential-ingredients-effective-onboarding-program.aspx))
- **1/3 to 2/3** of new hires that organizations often lose within their first 12 months on the job ([source](https://www.gallup.com/workplace/246242/essential-ingredients-effective-onboarding-program.aspx))
- **3.4x** as likely to feel onboarding succeeded when the manager takes an active role ([source](https://www.gallup.com/workplace/246242/essential-ingredients-effective-onboarding-program.aspx))

![Product manager reading notes on a laptop to learn an unfamiliar industry](https://images.lazur.app/content-images/problem/learn-unfamiliar-industry-first-90-days/learn-an-unfamiliar-industry-in-first-90-1-f2305d.jpg)

## 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.

| Window | Goal | Output |
| --- | --- | --- |
| Start | Set up your notes and ask for the team's reading list | One note page for the new domain |
| First week | Map the words used in meetings | A glossary with plain meanings and examples |
| Weeks 2 to 4 | Listen to customer and sales calls | A map of the buying process and the budget owner |
| Days 31 to 60 | Learn the money and the rules | A short summary of pricing, contracts, and data limits |
| Days 61 to 90 | Own one small decision | A written recommendation you can defend in a review |

_A rough 90 day sequence. Move faster or slower to match your team's pace._

## 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.

| Tool | Cost | Mac notes |
| --- | --- | --- |
| Anki | Free desktop app | Needs macOS 13 or later on Apple silicon or Intel |
| Obsidian | Core app is free without limits. The pricing page encourages a $50 per user per year commercial license for work use, but does not require it. | Notes are plain Markdown files. Current desktop version is 1.15.0. |
| Notion | Check their pricing page | Desktop app with databases, useful for the glossary table above |

_Check each vendor's own page before you commit to a plan._

## 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.

> **Check before you capture:** If a screen or document holds client, patient, or financial data, do not capture it until your employer confirms that the tool is allowed.

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](https://www.lazur.app/download) or compare plans on the [pricing page](https://www.lazur.app/pricing).

![Notebook and pen on a desk, ready for glossary notes on a new domain](https://images.lazur.app/content-images/problem/learn-unfamiliar-industry-first-90-days/learn-an-unfamiliar-industry-in-first-90-3-ef17f4.jpg)

## 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.

> **Ask for a review:** Ask a trusted colleague to read your glossary once. Ask them to mark every term they would not trust you to use in a meeting. Their marks show gaps your own review will miss.

## 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.

## With Lazur

Lazur is a voice assistant for the Mac that lives in the notch. Hold ⌥ ⌘ and ask; it sees your screen, answers out loud, points at buttons and walks you through apps. Hold fn to dictate. Free for 3 days, then $18/month: https://www.lazur.app/download

- “What does this term mean here?”: Lazur reads the term on screen, answers out loud, and points at where it appears. (Explains what's on screen)
- “Hold Option and Command on a term and ask what it means here.”: Lazur answers out loud from what is on your screen, so the answer matches the page you are reading.
- “Ask where the glossary database is in Notion.”: Lazur draws a circle and a label around the place on screen, so you find it without hunting.
- “Ask Lazur to research how public sources define a term.”: Lazur runs the search in its own Chrome tabs and returns a summary and a report you can check.
- “Hold fn and dictate a definition into your Obsidian note.”: Text lands at the cursor in any app, and your personal dictionary keeps odd industry terms spelled right.
- “Ask Lazur to walk you through making a Notion table.”: Lazur guides you one click at a time and waits for each click. It does not click for you.
- “Add a reminder to book a customer call on Thursday.”: Lazur adds it to Apple Reminders by voice, so the call stays on your list.

## A plan you can start this week

- **Morning: Short quiz from memory.** Open your Anki deck and answer every due card from memory before you check. Mark what you missed, then move on. Keep the session short enough that you do it every day, even on busy weeks.
- **In meetings: Capture unknown words.** Note each unfamiliar word during the meeting, not after. Type it fast, then keep listening. After the meeting, ask one colleague to define the two terms you care about most.
- **Tuesday: Talk to one customer or user.** Ask about the job they are trying to do, the step before they buy, and the person who signs off. Write their words in your glossary, not yours. Their vocabulary is the one your roadmap will be judged against.
- **Thursday: Read one rule source.** Pick one contract, policy, or data rule that limits your product. Read it end to end, then write a short summary in your own words. Mark anything you still cannot explain for your next review.
- **Friday: Check your progress.** Review the week's glossary additions. Answer the checkpoint questions out loud, then note the ones you stumbled on. Those become the first items for next week.

## FAQ

### Is 90 days enough to learn an unfamiliar industry?

A realistic goal for 90 days is working fluency. You can follow the words, the customers, and the main rules. Expertise takes longer. Gallup says most people take 12 months or more to get up to speed in most jobs, so plan for a longer tail after day 90.

### What should I learn first in a new industry?

Start with the words you hear in your next few meetings, because they show what people assume you already know. Then learn the customer's buying process, the money flow, and the rules that limit your roadmap. Keep a running list of questions for each area.

### Does rereading notes help me learn a new domain?

Not much, according to Dunlosky's review. It rated rereading and highlighting as less useful than practice testing and distributed practice. Close the doc, write the definition from memory, then check your answer.

### Does Lazur store my company's data?

Lazur keeps a memory of what you asked and did on your Mac. It sees your screen only while you hold the shortcut. Audio and screenshots go to AI providers to answer, and they are not stored. Follow your employer's rules before you use it on restricted data.

### Should I use Anki or Obsidian for this?

Use Anki for spaced quizzes on terms, and Obsidian for linked notes you write in your own words. Both have free core apps. Anki's desktop app supports macOS 13 or later. Obsidian's current desktop version is 1.15.0.

### Does Lazur run on Windows?

No. Lazur is a voice assistant for macOS, on Apple silicon and Intel Macs. Windows is planned, but it is not available yet.

### What if my new domain involves patient or client records?

Follow your employer's rules on that data before you use any tool, including notes, screenshots, and dictation. Ask your compliance or privacy team which tools are allowed. Treat this page as background reading, not as their answer.

## Sources

1. [Why the Onboarding Experience Is Key for Retention](https://www.gallup.com/workplace/235121/why-onboarding-experience-key-retention.aspx), Gallup, checked 2026-11-08
2. [Essential Ingredients for an Effective Onboarding Program](https://www.gallup.com/workplace/246242/essential-ingredients-effective-onboarding-program.aspx), Gallup, checked 2026-11-08
3. [This Fixable Problem Costs U.S. Businesses $1 Trillion](https://www.gallup.com/workplace/247391/fixable-problem-costs-businesses-trillion.aspx), Gallup, checked 2026-11-08
4. [Newcomer adjustment during organizational socialization: A meta-analytic review of antecedents, outcomes, and methods](https://pure.ul.ie/en/publications/newcomer-adjustment-during-organizational-socialization-a-meta-an/), University of Limerick (PURE), citing Journal of Applied Psychology 2007, checked 2026-11-08
5. [Distributed practice in verbal recall tasks: A review and quantitative synthesis](https://www.yorku.ca/ncepeda/publications/CPVWR2006.html), York University (N. Cepeda lab page), checked 2026-11-08
6. [Strengthening the Student Toolbox](https://www.aft.org/ae/fall2013/dunlosky), American Federation of Teachers, American Educator, checked 2026-11-08
7. [Anki Manual: Deck Options](https://docs.ankiweb.net/deck-options.html), Anki, checked 2026-11-08
8. [Anki](https://apps.ankiweb.net/), Anki, checked 2026-11-08
9. [Obsidian Pricing](https://obsidian.md/pricing), Obsidian, checked 2026-11-08
10. [Download Obsidian](https://obsidian.md/download), Obsidian, checked 2026-11-08