Checkpoint: Adoption at Scale

Question 1 of 5

• Accept it, because contributions are free capacity.
• Reject it and ask the team to delete it.
• Ask the core team to rebuild it properly first.
• Keep it local, built from system parts, and list it so a second team’s need can trigger an RFC.

Question 2 of 5

• Accept it through a brand token that switches the key handling.
• Treat it as a product proposal for both brands, decided in API review against the WAI-ARIA tabs pattern.
• Fork Tabs for Tidewater.
• Add a brand prop to Tabs.

Question 3 of 5

• Whether the scan counts something teams can copy, such as the nw-button class, instead of the component’s own marker.
• Whether users are using old browsers.
• Whether the survey sample was too small.
• Whether 88% is above the company target.

Question 4 of 5

• Let the engineer with more experience decide privately.
• Ship inline editing as an experimental flag and see what happens.
• Discuss it in the open API review using principles and usage evidence, then record the decision and reasons in the log.
• Postpone it until the next annual planning cycle.

Question 5 of 5

• Publish the ranking so low teams feel pressure to improve.
• Set Reporting a 90% target for next quarter.
• Ignore it, because adoption metrics are unreliable.
• Treat it as research: ask Reporting what the system lacks, and report organization-wide trends upward.