Workplace guides
Hard conversations, decoding the language of meetings, sending the email you mean to send.
How to tell your boss they're wrong without burning anything down. What "k." actually means in a text. The email you write at 11 PM versus the email you should send.
- How to figure out what career to switch to
- How to Make the Case for Your Promotion in Writing
- How to politely decline a meeting
- How to Push Back on a Decision That's Already Been Made
- How to see the real structure of a complex document
- How to Tell Your Boss a Deadline Is Unrealistic (Before It's Too Late)
- How to Test a Business Name Before You Commit to It
- How to Test If a Name Passes the Drunk Test
- How to Write Self-Review Bullets That Get You the Raise
- Is accounting going to be replaced by AI?
- What "Kindly" Actually Means at the Start of an Email (And Why It Lands So Differently)
- What "Let's Take This Offline" Actually Means in a Meeting (And When to Push Back)
- What jobs will be in demand in 5 years?
Quick answers to more workplace questions — each with the tool that does the heavy lifting.
Common Naming Mistakes That Kill Startups (and How to Avoid Them)
The pattern is more predictable than founders realize. Here are the seven mistakes that show up over and over.
- Mistake one: a name that has to be spelled, not heard
- Mistake two: trying to be too clever
- Mistake three: a name that locks you into one product
- Mistake four: a domain that is one letter off
- Mistake five: SEO already buried
🔍 NameAudit does this for you.
How to Brainstorm Names That Are Not Terrible
The reason most naming brainstorms produce nothing usable. And the structural change that fixes it.
- Brainstorm into categories, not into one big list
- Use a constraint to force creativity
- Steal patterns from companies you admire, not their words
- Brainstorm with someone who is not in your industry
- Sleep on the list and re-read it cold
⚡ NameStorm does this for you.
How to Break Down a Complicated Document Section by Section
Trying to read it all at once is the trap. Here's a five-step section-by-section method that gets you from 'I have no idea what this says' to 'I can act on this' in about an hour.
- Read each section's first and last paragraph first
- Pick one section and answer three questions
- Take notes in your own words, not the document's
- Stop after three sections, not when you're tired
- Reassemble at the end
🔍 PlainTalk does this for you.
How to bring a meeting back on topic
Real-time language for redirecting a meeting that has drifted — without shutting people down, dampening the energy, or making it awkward.
- Acknowledge what is happening before redirecting
- Name the time and the original topic
- Park the tangent explicitly
- Bring the original question back into focus
- Use group consent for time extensions, not unilateral decisions
🛡️ Meeting Hijack Preventer does this for you.
How to Choose Between Two Job Offers (When Both Look Good)
Salary is not the right comparison. Career trajectory, leverage on your current skills, and what each option gives you next are. Here is the framework.
- Compare three years out, not Day 1
- Measure leverage on your current skills, not just absolute fit
- Weight the people heavily
- Treat optionality as a real factor
- If it is genuinely 50/50, pick the harder one
⚖️ Leverage Logic does this for you.
How to Come Up With a Business Name (When You Are Stuck)
Most naming guides give you exercises. Here is the actual structured approach that surfaces good names.
- Write down what the business does in plain language
- List adjacent words and concepts, not synonyms
- Run the words through five style categories
- Generate volume. Then ruthlessly filter.
- Audit the survivors before you fall in love
⚡ NameStorm does this for you.
How to Decide Between Multiple Side Projects (When You Cannot Do Them All)
Three exciting ideas, ten hours a week. Here is how to pick the one with the highest leverage, instead of doing all three poorly.
- Score each project on what it leverages from your current skills
- Score each project on what it produces beyond itself
- Honestly estimate the time, then double it
- Pick one — and put the other two on a list, not in your head
- Set a real review point, not an open-ended commitment
⚖️ Leverage Logic does this for you.
How to find the action items buried in a long document
A method for the specific problem of pulling out the things you actually have to do from a document that buried them in pages of context, throat-clearing, and FYI material.
- Search for action verbs first
- Search for dates and deadlines
- Search for direct address language
- Map each action item to a person and a deadline
- Build a one-page summary of the actions and ignore the rest
🔇 Noise Canceler does this for you.
How to Handle a Flood of Emails After Vacation (Without Undoing the Vacation)
Two hundred unread. The trip you just took is in danger of evaporating in your first hour back. Here's how to face a flooded inbox without re-entering work in panic mode.
- Don't read them on Sunday night
- Block your first ninety minutes for triage only
- Sort by sender and look for patterns
- Archive anything older than your last day out
- Send one 'catching up' to the few that matter
📬 Email Urgency Triager does this for you.
How to handle someone who dominates meetings
A method for managing the colleague who talks over everyone, takes up most of the air time, and somehow ends up running every conversation — without making it personal.
- Use structural redirects, not personal ones
- Call on quiet people by name
- Set explicit speaking order at the start
- Have a one-on-one offline if it is chronic
- Recognize when the dominator is the boss
🛡️ Meeting Hijack Preventer does this for you.
How to Hold Someone Accountable in Writing Without Making It Personal
Accountability in writing is documentation, not punishment. Five steps for raising a real issue with a colleague in writing — clear enough that nothing is ambiguous, professional enough that the relationship survives.
- Separate the behavior from the person
- Name the specific commitment, not the general expectation
- Lead with the impact, not the offense
- Ask what changed and what you can do — don't lecture
- Know when accountability in writing is the wrong tool — and when it's the right one for the wrong reason
🔨 Velvet Hammer does this for you.
How to identify your transferable skills
A method for figuring out which of your current skills will travel to a new role or industry — and how to talk about them so a new employer recognizes their value.
- Strip the industry language out
- Group your work into reusable competencies
- Find the equivalent terms in the target field
- Anchor each skill in a specific story
- Ask someone in the target field to gut-check
🗺️ Skill Gap Map does this for you.
How to Know If an Email Is Actually Urgent
The subject line says URGENT. The body has three exclamation points. Your stomach flips. Here's how to read past the volume and tell whether anything actually has to happen today.
- Strip the punctuation, then read the request
- Look for a real deadline, not a manufactured one
- Check whether the sender controls the urgency
- Apply the 24-hour test
- Trust the calmness signal
📬 Email Urgency Triager does this for you.
How to Know if an Opportunity Is Worth the Time
Some opportunities pay off enormously. Some are expensive distractions disguised as opportunities. Here is how to tell the difference before you commit.
- Calculate the real time cost, not the advertised time cost
- Identify what you actually get, in concrete terms
- Apply the opportunity-cost test
- Be skeptical of opportunities that flatter you
- Decline more often than you think you should
⚖️ Leverage Logic does this for you.
How to know if you're ready for the next level
An honest read on whether you are ready for promotion or a step up — what the actual signals are, and how to know when to push for it.
- You are already operating at the next level on most days
- Your manager mentions you in next-level contexts
- Peers from the higher level treat you as a peer
- You can articulate what is left to demonstrate
- If you're ready and they're not moving, ask explicitly
🗺️ Skill Gap Map does this for you.
How to Know If Your Business Name Is Forgettable
The tests that reveal whether your name will stick — and the difference between a name people forget and a name people remember.
- Run the day-after test
- Check whether the name evokes a concrete image
- Try the 'tell a friend' test
- Audit the phonetic profile
- If the name is forgettable, change one variable, not all five
🔍 NameAudit does this for you.
How to know if your job is at risk
An honest diagnostic for whether your specific role is at risk from automation, restructuring, or industry decline — and what to do about it.
- Look at what your work actually consists of, in percentages
- Notice what your company has been investing in
- Check whether your industry as a whole is shrinking or growing
- Talk to people who left your role two to five years ago
- Plan as if the risk is real, even if it might not be
🔮 Future Proof does this for you.
How to know what emails actually need a response
A diagnostic for telling which emails actually require your reply and which are informational, social, or noise — so you can stop responding to everything.
- Look for an explicit request or question
- Check who else is on the email
- Notice whether the email is the start or middle of a thread
- Distinguish 'reply expected' from 'reply traditional'
- When in doubt, wait 24 hours
📬 Email Urgency Triager does this for you.
How to make sure quiet people speak up in meetings
A method for drawing out the team members who have valuable ideas but rarely contribute in real time — without putting them on the spot or making it weird.
- Send the agenda and key questions in advance
- Use round-robin formats for important topics
- Use chat or written input for fast-moving discussions
- Wait longer after asking a question
- Acknowledge contributions specifically and warmly
🛡️ Meeting Hijack Preventer does this for you.
How to manage email overload
A practical method for handling an inbox that has more incoming volume than you can possibly read carefully — without dropping the things that actually matter.
- Accept that you will not read every email
- Triage in batches, twice a day
- Use the 'four-D' rule for fast triage
- Set up filters and rules to handle predictable volume
- Lower your response standards on non-urgent emails
📬 Email Urgency Triager does this for you.
How to Name a Startup When All the Good Names Are Taken
The .com is gone, the obvious words are claimed. Here is how the people naming new companies right now actually do it.
- Look outside English
- Use compound words
- Add a soft modifier
- Use a real word that means something tangentially related
- Avoid the 'creative spelling' trap
⚡ NameStorm does this for you.
How to Name Your Company When You Have No Creative Ideas Left
You have stared at a blank page for a week. Here is the structured approach that does not require inspiration to work.
- Steal vocabulary instead of generating it
- Combine words by rule, not by inspiration
- Use AI as a generator, not as the decider
- Sleep on the list
- Pick something good enough and ship
⚡ NameStorm does this for you.
How to Push Back on an Unreasonable Email Without Burning the Bridge
Pushing back in writing is harder than pushing back in person — there's no tone, no read on the room, no chance to adjust mid-sentence. Five steps for declining or challenging a request in email without making the relationship worse than the request was.
- Reply when you're calm — but reply, don't disappear
- Restate the request before you respond to it
- Push back on what specifically, not on the request in general
- Offer a path, not just a refusal
- Know when 'without burning the bridge' is no longer the goal
🔨 Velvet Hammer does this for you.
How to read a financial report like an expert
A practical method for reading a financial report so you can actually understand what is happening at a company — not just what they want you to think.
- Skip the front, go straight to the financials
- Read the cash flow statement before the income statement
- Read the footnotes — that is where the secrets are
- Compare year over year, and look for patterns
- Compare to peers, not just to itself
🔍 PlainTalk — Document Analyst does this for you.
How to read a job offer letter or employment contract before signing
A specific method for understanding what you are actually agreeing to in a job offer or employment contract — before you sign and before you negotiate.
- Find the compensation section and verify everything in writing
- Read the at-will and termination language carefully
- Look for non-compete and non-solicitation clauses
- Read the IP assignment section
- Identify what is missing
🗡️ Jargon Assassin does this for you.
How to read a long policy update without losing your mind
A method for reading the long policy update that just landed in your inbox without giving up halfway through and without missing the parts that matter.
- Look for the changes, not the document
- Scan for changes to your obligations or costs
- Watch for arbitration and waiver clauses
- Note any deadlines or default-acceptance language
- Save the old version if you can find it
🔇 Noise Canceler does this for you.
How to Read a School Newsletter or HOA Notice Efficiently
Most of it is for someone else. A small fraction will land you in trouble if missed. Here's how to skim community communications and catch the parts that affect you.
- Filter by your kid, your address, your committee
- Read every date and dollar amount
- Look for the words 'mandatory' and 'required'
- Skip everything addressed to a different audience
- Add the items to your calendar immediately
🔇 Noise Canceler does this for you.
How to read a software license agreement before clicking accept
A practical method for actually reading the software license agreements you click through every week — at least the parts that matter — without spending an hour on each one.
- Search for "data" — what they collect and what they do with it
- Search for "arbitration" or "class action"
- Search for "license" — what you are getting and what you are not
- Look for content ownership
- Note termination and account deletion terms
🗡️ Jargon Assassin does this for you.
How to Read an Insurance Policy You Actually Need
The policy is sixty pages. The claim is what you'll care about. Here's how to read auto, home, or renters insurance so you know what you're covered for — before you need it.
- Read the declarations page first
- Find the deductible and the out-of-pocket maximum
- Read the exclusions before the coverage
- Distinguish 'named perils' from 'all perils'
- Verify the limits cover what you actually have
🗡 Jargon Assassin does this for you.
How to read between the lines of a performance review
A method for understanding what your performance review is actually saying — including the parts your manager could not put in writing.
- "Meets expectations" usually means just enough
- Specific praise is real, generic praise is filler
- Watch for 'developing' and 'continued growth' language
- Notice the proportion of feedback areas to strengths
- Compare to your peers if you can
🔍 PlainTalk — Document Analyst does this for you.
How to Respond to a Passive-Aggressive Email Professionally (Without Matching the Energy)
Passive-aggressive emails work by smuggling hostility past plausible deniability. The response that lands is the one that addresses the smuggled content without picking up the deniability. Five steps for not getting played.
- Don't match the energy — name the underlying concern instead
- Pretend it was sincere
- Resist quoting their email back at them
- Decide whether to address the issue or the pattern
- Know when not engaging is the right move
🔨 Velvet Hammer does this for you.
How to run a meeting that doesn't go off the rails
A method for running a meeting that stays on topic, ends on time, and produces a decision — without you turning into the strict person who shuts down conversation.
- Have a real agenda, with topics and times
- State the desired outcome at the start of each topic
- Use a parking lot for tangents
- Hold the time
- Close with explicit decisions and owners
🛡️ Meeting Hijack Preventer does this for you.
How to Say No to Your Boss (Without Burning a Bridge)
Saying no to your manager isn't insubordination — it's scope management. The trick is saying it in a way that shows judgment, not reluctance.
- Don't answer immediately
- Confirm you understood the request
- Name the tradeoff, not the refusal
- Offer a partial yes
- Follow through on whatever you did commit to
✋ Difficult Talk Coach does this for you.
How to set a meeting agenda that actually works
A practical method for writing agendas that actually shape what happens in the meeting — not the bullet-list versions everyone ignores.
- Define the meeting's purpose in one sentence
- Time-box each item with specific minutes
- State the desired outcome for each item
- Identify a primary contributor or owner for each item
- Send the agenda 24 hours ahead, not at the start
🛡️ Meeting Hijack Preventer does this for you.
How to skim a long document without missing the important parts
A method for reading a long document fast — extracting what actually applies to you while not getting blindsided by something you skipped.
- Identify what kind of document it is and what you would care about
- Scan for action language
- Look for numbers, especially money and dates
- Filter against your specific situation
- Set the document aside and write down what you took away
🔇 Noise Canceler does this for you.
How to skim a long email and not miss anything important
A method for processing the email that is way too long without spending fifteen minutes on it or missing the one thing that needed your attention.
- Read the first sentence and the last paragraph first
- Search for question marks
- Look for explicit action language
- Identify any dates and deadlines
- If you skimmed and feel uncertain, ask a clarifying question instead of re-reading
🔇 Noise Canceler does this for you.
How to Spend Your Free Time When You Want a Career Change
Ten hours a week is not nothing. Here is how to spend it on the highest-leverage moves toward a different career, without quitting first.
- Build something concrete in the new field, not credentials
- Find one person doing what you want to do, and learn from them specifically
- Take on small paid work in the new field, even at a loss
- Be explicit about your current job's role in the transition
- Set a 12-month checkpoint, not an indefinite timeline
⚖️ Leverage Logic does this for you.
How to spot manipulative clauses in any contract
A practical method for catching the clauses in any contract that are written to disadvantage you — without needing to be a lawyer.
- Look for asymmetric remedies
- Watch for unilateral modification rights
- Read mandatory arbitration and class-action waiver clauses carefully
- Notice indemnification scope
- Find and challenge any 'sole discretion' language
🗡️ Jargon Assassin does this for you.
How to Spot the Highest-Leverage Thing You Could Be Doing
Most of your time goes to things with low yield. Here is how to find the small set of activities that produce most of the results, and shift your time toward them.
- Audit a recent successful week — what produced the results
- Identify the activity with the largest gap between yield and time spent
- Test for the constraint, not the accelerant
- Move time from low-yield to high-yield, not from rest to either
- Reassess every quarter — leverage points move
⚖️ Leverage Logic does this for you.
How to Spot What's Actually Changed in a Terms of Service Update
The email said 'we're updating our terms.' The PDF is 31 pages. Here's how to find the four things they actually changed — without reading the 27 pages that are identical to last time.
- Look for the change log at the top
- Diff against the previous version
- Focus on data, billing, arbitration, and rights granted
- Watch for an opt-out window
- Decide before the deadline, not after
🔇 Noise Canceler does this for you.
How to stop email anxiety
A practical approach to the specific anxiety that follows you all day because of the unread emails you have not gotten to — and how to make it stop.
- Turn off all email notifications
- Set fixed email windows and protect them
- Remind yourself that almost nothing is actually urgent
- Lower the stakes of being late
- If anxiety persists, look at the underlying issue
📬 Email Urgency Triager does this for you.
How to suggest making a meeting async
Specific language for proposing that a meeting become a written or recorded async exchange — without sounding like you are trying to get out of work.
- Frame it as making the meeting better, not avoiding it
- Propose a specific async alternative
- Acknowledge the parts that genuinely need to be sync
- Offer to set up the async piece yourself
- Accept gracefully if the answer is no
🕵️ Meeting BS Detector does this for you.
How to switch careers to tech
A practical roadmap for moving into a tech role from a non-tech background — what to actually learn, what to skip, and how long it really takes.
- Pick a specific role, not "tech" as a category
- Audit what you already have
- Learn the smallest thing that lets you start applying
- Build a public portfolio, however small
- Plan for it to take twelve to eighteen months
🗺️ Skill Gap Map does this for you.
How to Talk About Your Work Without Sounding Arrogant
Five techniques to claim credit cleanly. Specific over superlative, decision over outcome, and the team mention that does not feel like a dodge.
- Talk about what you decided, not how you performed
- Use specific numbers instead of superlatives
- Mention the team without using them as a shield
- Acknowledge what was hard or what you got wrong
- Stop talking after the answer
🏆 Brag Sheet Builder does this for you.
How to tell if a meeting is going to be useful
A diagnostic for predicting which meetings on your calendar will be worth your time and which will not — before you commit your hour to them.
- Look at the agenda — or the absence of one
- Check the attendee count
- Ask whether a decision will be made
- Notice the timing pattern
- Trust your prior with this organizer or this meeting type
🕵️ Meeting BS Detector does this for you.
How to Tell If Your Name Is Too Similar to an Existing Brand
A trademark search is not enough. Here is the broader test for whether a name is going to cause confusion — or a lawsuit.
- Run the trademark search across the right classes
- Search the name plus your industry on Google and social
- Use the customer-confusion test
- Pay attention to the size and litigiousness of the other side
- If you find a real collision, change the name now
🔍 NameAudit does this for you.
How to Tell What a Document Is Actually Saying (vs. What It Sounds Like)
Some documents are designed to read favorably and decide unfavorably. Here's how to read past the tone and find what the words actually commit to — or don't.
- Separate verbs of doing from verbs of intending
- Underline every modal verb
- Find the conditions hidden in subordinate clauses
- Notice what isn't denied
- Read the silence in the document
🔍 PlainTalk does this for you.
How to Tell Your Boss They're Wrong (Without Burning Anything Down)
You can see the problem clearly. The hard part is saying so. A practical, step-by-step approach to pushing back on your manager — professionally, and without blowing up your career.
- Pick a private moment, not a public one
- Lead with a question, not a correction
- Name the problem, not the person
- Predict their pushback before you walk in
- Practice your opening line out loud
🗣 Difficult Talk Coach does this for you.
How to Tell Your Manager Their Feedback Feels Unfair (Without Sounding Defensive)
Unfair feedback stings twice — once when you hear it, and again every time you replay it. The trick is responding with evidence instead of emotion, and doing it when the conversation can still change.
- Separate the feedback from the verdict
- Ask for the specifics before you argue
- Bring the paper trail
- Frame it as accuracy, not injustice
- Document the resolution, whatever it is
⚖️ Difficult Talk Coach does this for you.
How to translate a confusing document into plain language
A method for taking a document that was clearly not written for you and figuring out what it actually says, in language you would use yourself.
- Identify what kind of document it is and who it is for
- Find the structural skeleton before reading the prose
- Translate sentence by sentence with simpler words
- Identify obligations and timelines and write them down separately
- Look for what the document is not saying
🔍 PlainTalk — Document Analyst does this for you.
How to triage your inbox in 5 minutes
A specific protocol for opening your inbox, identifying the urgent stuff, and closing the inbox — all in five minutes, several times a day.
- Sort by sender or subject, not chronologically
- Scan only the From and Subject columns
- Open only the urgent flagged items
- Close the inbox without reading anything else
- Do this multiple times a day, not constantly
📬 Email Urgency Triager does this for you.
How to Understand a Document Written in Academic Jargon
Academic writing is dense by training, not by accident. Here's how to read papers, abstracts, and reports written in academic register — and find the actual finding underneath.
- Read the abstract last, not first
- Find the figure that summarizes the result
- Translate the technical terms only as needed
- Read the discussion to see what authors think
- Watch for hedging language in the conclusions
🔍 PlainTalk does this for you.
How to understand a document written in jargon
A method for cracking documents that are written in specialist vocabulary — academic, legal, technical, medical — when you are not the specialist.
- Build a quick glossary before reading
- Read the abstract, conclusion, or executive summary first
- Translate one paragraph at a time, in your own words
- Notice the structure of argument or evidence
- Ask someone in the field to gut-check your reading
🔍 PlainTalk — Document Analyst does this for you.
How to Write a Professional Email When You're Actually Furious
The professional email written from a furious place is a different animal from the one written from a calm one. Five steps for getting from rage to a message that lands without leaking the rage into it.
- Buy yourself a window — but write something now
- Write the rage draft as the diagnostic, not the deliverable
- Translate the content, don't sand the tone
- Match the level to the situation, not to your anger
- Know when 'professional email' is the wrong tool entirely
🔨 Velvet Hammer does this for you.
How to Write Resume Bullets for the Job You Actually Did
Most resume bullets describe the role, not the work. The five-part formula that captures what you actually did and why it mattered.
- Start with a strong verb that names the action
- Name the scope: what, where, how big
- Add the constraint or judgment that made it hard
- End with the outcome in numbers when possible
- Cut everything that is not the bullet
🏆 Brag Sheet Builder does this for you.
Is it too late to learn coding?
An honest answer to whether learning to code in 2026 is still worth it — given AI, given market changes, given how much your starting point has shifted.
- The bar to becoming a software engineer has moved up
- Learning to code as a multiplier on what you already do is more valuable than ever
- AI raises the floor and lowers the ceiling differently than people think
- The kind of coding that is most worth learning has shifted
- It is not too late, but the destination is different
🔮 Future Proof does this for you.
Should this be a meeting or an email?
An honest test for whether the meeting on your calendar — or the meeting you are about to schedule — should actually be a meeting at all.
- If it is information flowing one way, it is an email
- If there is no decision to make, it is probably not a meeting
- If it requires real-time back-and-forth, it is a meeting
- If it can wait 24 hours, it can be async
- If you cannot name the agenda in three sentences, do not have it
🕵️ Meeting BS Detector does this for you.
Signs your meeting could be an email
Specific signals that a meeting on your calendar — or one you are about to schedule — is unnecessary and should be replaced with written communication.
- The agenda is "status update" or "sync"
- There are more than eight people
- The same meeting has happened before with no new outcome
- No decision needs to be made
- The meeting could be skipped without anyone noticing
🕵️ Meeting BS Detector does this for you.
The Email You Write at 11pm vs. The Email You Should Send in the Morning
The 11pm email and the 8am email are written by different people, even when both are you. Five steps for using the difference rather than fighting it — write the late-night version, but send the morning one.
- Recognize the 11pm self and the 8am self are not the same writer
- Use the 11pm self for diagnosis, not delivery
- Don't trust the 11pm verdict on whether to send
- Read the morning version aloud before sending
- Know when no email at all is the morning answer
🔨 Velvet Hammer does this for you.
What "K." Actually Means in a Text (And Why the Period Changes Everything)
'k' and 'K.' look almost identical and mean completely different things. Five contexts that decode what 'K.' is actually doing — and why the period is doing most of the work.
- Read the no-period version (it's almost always fine)
- Spot the period that closes the conversation
- Recognize the cool response
- Notice the angry version
- Know what the pattern means
🔍 Decoder Ring does this for you.
What "Let's Table This" Actually Means in a Meeting (And When It's a No)
'Let's table this' usually means defer — but sometimes it means no, sometimes it means dead, and in the UK it means the opposite. Five contexts and how to tell which one you got.
- Read the legitimate defer
- Spot the 'we'll come back to this' version
- Recognize the polite no
- Notice the conflict-defer
- Know the pattern that means it's dead
🔍 Decoder Ring does this for you.
What "Noted" Actually Means in a Work Email (And What to Say Back)
Someone replied 'Noted.' to your email and your brain freezes. Four contexts, what each one really means, and how to respond — including the one that's actually a flag.
- Read the routine acknowledgment
- Spot the parked disagreement
- Recognize when they heard the criticism
- Notice when 'Noted' means stop
- Know the one that needs attention
🔍 Decoder Ring does this for you.
What "Per My Last Email" Actually Means (And How to Respond Without Escalating)
'Per my last email' isn't always passive-aggressive. Four contexts, what each one really signals, and how to respond in a way that doesn't make the situation worse.
- Read the polite reference
- Spot the 'I already answered this' version
- Recognize the status move
- Notice the paper-trail version
- Know the pattern that needs attention
🔍 Decoder Ring does this for you.
What does an arbitration clause actually mean for you?
An honest explanation of what mandatory arbitration clauses actually do — what rights you give up, when it might be okay, and when to push back.
- You give up your right to sue in court
- You usually give up the right to join class actions
- The arbitrator is not as neutral as the marketing suggests
- Arbitration is private, which protects the company's reputation
- Many arbitration clauses have opt-out windows
🗡️ Jargon Assassin does this for you.
What Makes a Name Memorable (and What Just Sounds Memorable to You)
There is a real list of properties memorable names share. Here is what it actually is — and what is just survivor bias.
- Concreteness beats abstraction
- Distinctiveness within the category beats absolute distinctiveness
- Pronounceability matters more than length
- Rhythm and stress patterns embed names without effort
- Ignore: 'easy to spell' as a memorability rule
⚡ NameStorm does this for you.
What skills are actually future-proof?
An honest answer to which skills are actually durable across the next decade — separating fundamentals that hold from trends that will not.
- Writing — clearly, in any medium
- Working effectively with AI tools
- Understanding people — calibration, persuasion, trust-building
- Building things from scratch
- Deep specialization in something AI is bad at
🔮 Future Proof does this for you.
What skills do I need to become a product manager?
An honest breakdown of the skills that actually matter for product management — what hiring managers look for, what the job descriptions overstate, and what nobody mentions until you are doing the work.
- Communication that lands across audiences
- Decision-making under uncertainty
- Enough technical understanding to be useful, not enough to code
- Customer empathy that is specific, not abstract
- Data fluency without data obsession
🗺️ Skill Gap Map does this for you.
What to actually pay attention to in a benefits packet
A practical guide for the annual open-enrollment benefits packet — what is worth your time, what to ignore, and what people most often miss until it costs them.
- Compare medical plans by your expected total cost, not by premium
- Take the HSA seriously if it is offered
- Check whether your employer matches the 401(k) and whether you are leaving money on the table
- Skip most of the supplemental insurance unless you have a specific reason
- Note the deadlines and the default if you do nothing
🔇 Noise Canceler does this for you.
What to do when you have 1000+ unread emails
A method for the specific situation where your inbox has grown to a size where you cannot possibly read it all — and what to do to recover without dropping anything important.
- Declare email bankruptcy and archive everything older than 30 days
- Send a brief 'inbox bankruptcy' note to anyone you know was waiting
- Process the remaining 30 days using fast triage
- Set up filters so this does not happen again
- Forgive yourself and move on
📬 Email Urgency Triager does this for you.
What to look for in an NDA before signing
A practical guide to reading non-disclosure agreements — what they should and should not say, and what to push back on.
- Verify it is mutual or one-way, and understand which
- Read the definition of 'confidential information'
- Check the duration
- Identify the carve-outs
- Look for non-compete-by-stealth language
🗡️ Jargon Assassin does this for you.
What to Say in a Performance Review When You Cannot Remember
Memory failure is normal — the year is long. Five questions and a pre-meeting protocol that pull the work back into focus.
- Walk your calendar by quarter
- Skim your sent email and Slack mentions
- Ask: what did I unblock for someone else?
- Ask: what would have gone wrong if I had not been there?
- Write a draft, then ask a trusted peer to add what you missed
🏆 Brag Sheet Builder does this for you.
Looking for something different? See all guides or browse by tool.