Synthesis Whiteboard Framework: Pitfalls & Red Flags

Pitfalls and red flags

Pitfalls & Red Flags for Synthesis Whiteboard Framework focuses on answer completeness score, mechanism-first explanation quality. The goal is to connect observed QoR movement to mechanism, ownership, and regression risk.

• Dashboard trend breaks without recorded manifest changes.

• dont_touch list grows without periodic removal review.

• Retiming gains claimed without formal evidence.

• Topographical numbers treated as final signoff.

• Fix improves one lane but silently regresses another.

Layer responsibility check

SYNTHESIS OWNERSHIP LAYERS — Synthesis Whiteboard Framework

layer               owns                          failure mode
----------------    ---------------------------   -------------------------
constraints         clocks/exceptions/policy      fake QoR optimism
mapping             cell choices/structure        depth/fanout regressions
optimization        timing/power tradeoffs        one-metric overfitting
physical-aware      topo/congestion estimates     handoff delta surprises
closure             ECO order/regression          fixes break other corners

Synthesis deep dive

Interview readiness comes from repeatable QoR reasoning under pressure.

Concept diagram

INTERVIEW ANSWER SHAPE

context -> metric -> mechanism -> fix -> regression -> ownership

Metric graph

PANEL SCORING

clarity      ███████
mechanism    ██████
regression   █████

Reports and artifacts

• mock scorecard

• scenario debrief

• Q&A coverage

• framework adherence

Mini case study

Candidate improved by replacing tool-command answers with evidence-driven closure narratives.

Debug branches

• State assumptions first

• Defend option tradeoffs

• Close with rollback/regression

Senior review question

Ask: what evidence proves this QoR move is real and stable?

Key takeaways

• State exact run context (RTL, SDC, libs, switches) with every QoR claim.

• Re-run timing, area, and power regressions after each synthesis ECO.

Common pitfalls

• Comparing runs with mismatched constraints or library views.

• Timing-only fixes that violate power or area budgets.

• Skipping equivalence checks after structural changes.

Principal synthesis review addendum

Strong synthesis answers narrate constraint intent, mapping path, QoR evidence, and regression risk in a fixed reusable structure.

Metric: answer completeness score, mechanism-first explanation quality