Amazon Forte vs 1on1 Cheatsheet for Performance Feedback: Which Wins?

TL;DR

Forte is the system, but 1on1s are the signal — the real differentiator in Amazon performance reviews isn’t documentation, it’s narrative control. Most managers rely on Forte to track goals, but the strongest candidates weaponize 1on1s to shape perception. The win isn’t in logging updates — it’s in framing outcomes as leadership principle demonstrations. Choose neither: master both, but let 1on1s drive the story.

Who This Is For

You’re a mid-level PM or IC at Amazon with 2–5 years in the org, preparing for your next review cycle, likely aiming for a promotion or strong PIP score. You’ve been told “your work speaks for itself” — and you’re starting to realize that at Amazon, it doesn’t. You need to translate output into observable leadership, and you’re deciding where to invest: rigorous Forte tracking or disciplined 1on1 prep. This is for you.

Is Forte Enough for a Strong Performance Review?

Forte alone will not save you in your Amazon performance review — it’s a ledger, not a case. In a Q3 HC meeting I sat in on, a L6 TPM had flawless Forte entries: 100% goal completion, on-time delivery, no outages. Yet the committee rejected her promotion. Why? “No evidence of raising the bar.” Forte showed what she did, not how she led.

The system is designed for traceability, not advocacy. You input goals, link them to LPs, mark completion — but that data is never read front-to-back by reviewers. Instead, it’s mined for keywords during HC debates. A red flag goes up when there’s no peer feedback, no stretch initiatives, or recurring dependency on others.

Not tracking goals, but pattern recognition — HC looks for consistency in raising standards, not just hitting them. One L5 SDE I reviewed had missed two Forte updates but included unprompted customer escalation resolutions and mentored three junior engineers — all surfaced in peer NPS comments. He got promoted.

Forte is table stakes. It proves you’re operational. But it doesn’t prove you’re exceptional. That comes from elsewhere.

Do 1on1s Actually Influence Performance Ratings?

Your 1on1s are your shadow performance review — every conversation shapes your manager’s memory, which becomes your case. In a debrief for a L6 DS candidate, the bar raiser said, “I don’t see innovation,” but the hiring manager pushed back: “She’s been driving experimentation culture in every sync — I’ve documented it for months.” That single line changed the outcome.

Here’s how it works: managers don’t write your BRD (Bar Raiser Document) from scratch. They pull from mental models formed in 1on1s. If you’ve consistently framed your work as customer-obsessed problem solving — not task reporting — you’re scripting their narrative.

A strong 1on1 isn’t status updates. It’s structured around three layers:

What happened (fact)
Why it matters (judgment)
What I’d do differently (ownership)

Bad 1on1s: “Launched A/B test on checkout flow.”

Good 1on1s: “We found 12% drop-off at step 3 — hypothesized friction in error messaging. Ran an A/B test that reduced drop-off by 4%. Learned that error tone impacts trust more than layout. Scaling this insight to auth flow next.”

Not activity reporting, but insight curation. The second version surfaces Dive Deep, Customer Obsession, and Learn and Be Curious — without naming them.

1on1s don’t influence ratings — they determine them by shaping the only narrative that matters: your manager’s.

How Do You Align Forte with Leadership Principles Without Gaming the System?

You don’t “align” Forte with LPs — you anchor each goal to a demonstration of principle application, not a label. In a HC for a L5 PM, one candidate tagged every goal with “Customer Obsession.” The bar raiser called it out: “This isn’t alignment — it’s checkbox theater.”

The difference? Depth over decoration. Instead of tagging, write updates that show the principle in action:

Bad: “Improved search relevance. LP: Customer Obsession.”
Good: “Discovered users abandoning search after 3 attempts — investigated logs and found typo tolerance failures. Partnered with NLP team to redesign fallback logic, reducing zero-result queries by 27%. Now documenting pattern for other teams.”

Now you’re showing Customer Obsession and Invent and Simplify.

One insight from a former bar raiser: “We look for spillover.” Did your work change how others operate? Forte entries that end with “shared learnings” or “adopted by X team” signal scale.

Not tagging principles, but proving propagation. The system rewards evidence of influence, not self-annotation.

A L6 applied this in 2023: his Forte update on a latency fix included a link to an internal talk he gave, with 42 attendees from 8 teams. That single line shifted perception from “fixer” to “teacher.” He got promoted.

What Should You Track in 1on1s to Win at Review Time?

Track three things in every 1on1: decisions influenced, risks surfaced, and feedback given upward. Not tasks — judgment moments.

In a debrief for a rejected L6 candidate, the feedback was: “Executes well, but no evidence of independent judgment.” His manager admitted: “He never challenged me on roadmap trade-offs.” That silence was interpreted as lack of ownership.

Contrast that with a successful L5: her 1on1 notes (shared with me as HC) showed:

“Pushed back on Q3 launch date — argued for additional dogfooding. Delayed by 2 weeks, reduced P0 bugs by 60%.”
“Flagged storage cost spike in preview environment — led investigation, saved $180K/yr.”
“Advised EM on onboarding new PM — suggested pairing with senior BPs first.”

These weren’t goals. They were discretionary interventions — the raw material of ownership.

Your 1on1 doc should be a battlefield map of your influence, not a to-do list.

Not what you did, but where you stepped in without being asked. Amazon promotes people who operate above their level — and that behavior is only visible in 1on1 records.

How Do You Prepare for HC When Your Manager Is Passive?

You own the narrative when your manager won’t — and Forte and 1on1s are your only leverage. In 2022, I reviewed a L6 candidate with a disengaged EM. His manager’s BRD was thin: two paragraphs, no peer feedback. But the candidate had maintained a shared 1on1 doc with detailed contributions — including emails where he’d escalated a compliance risk the EM had missed.

We used those to reconstruct his case. He got promoted — not because of his manager, but in spite of them.

Here’s the protocol:

Export all 1on1 notes — highlight moments of judgment, escalation, mentorship.
Populate Forte retroactively — link key decisions to goals, even if delayed.
Seed peer feedback — ask 3–5 colleagues to submit Forte comments before HC season.

One SDE I coached did this: he hadn’t updated Forte in 5 months. But he had 18 shared 1on1 docs with specific technical leadership examples. He attached them as “evidence addenda” — and won.

At Amazon, the process assumes manager advocacy. When it’s absent, you must become your own bar raiser.

Not waiting for sponsorship, but building self-sourced proof. The system allows it — barely — but only if you act early.

Preparation Checklist

Audit your Forte entries: are they outcome-focused, not task lists? Replace “delivered X” with “achieved Y, impact Z.”
Structure every 1on1 around decision-making, not status. Use the 3-layer model: fact, judgment, ownership.
Capture peer feedback in Forte — request specific comments from 3+ collaborators before review season.
Document upward feedback — if you’ve challenged roadmap, resourcing, or design, log it in 1on1 notes.
Retroactively tag major initiatives in Forte with Leadership Principles — but only if you show how they were applied.
Work through a structured preparation system (the PM Interview Playbook covers Amazon performance narratives with real HC debrief examples from 2022–2023 cycles).
Block 2 hours every quarter to rebuild your story — align Forte, 1on1s, and peer input into a single leadership arc.

Mistakes to Avoid

BAD: “I updated Forte every week — my manager should know what I’ve done.”
GOOD: “I used Forte updates as evidence, but shaped the story in 1on1s — framing each win as a leadership principle in action.”

BAD: “My 1on1s are just check-ins — I don’t want to overload my manager.”
GOOD: “I treated 1on1s as review prep — surfacing judgment calls, risks, and cross-team influence monthly.”

BAD: “I waited for my manager to write my BRD.”
GOOD: “I drafted my own case using Forte and 1on1 data — gave it to my manager as a starting point.”

FAQ

Does Amazon HC read Forte directly?

No — HC doesn’t open your Forte portal. They read summaries pulled by your manager or bar raiser. Forte’s value is in supplying evidence, not forming narrative. Entries matter only if they’re cited. A single peer comment in Forte that says “She unblocked our team’s API launch” is worth more than ten completed goals.

Can you get promoted without a strong 1on1 history?

Yes, but only if you have exceptional peer or skip-level sponsorship. Most candidates without documented 1on1 influence are seen as executors, not leaders. One L5 got promoted after presenting a “decision journal” at HC — but that’s rare. Default path: 1on1s shape memory.

Should you share Forte updates with your manager monthly?

Only if they’re reframed as leadership moments — not data dumps. One SDE sent a monthly “impact brief” with 3 wins, each tied to an LP. His manager used it verbatim in the BRD. Not sharing output, but packaging judgment — that’s the move.amazon.com/dp/B0GWWJQ2S3).

Your next 1:1 doesn't have to be awkward.

Available on Amazon → — scripts for tough conversations, promotion asks, and managing up when your manager isn't great.