The part nobody mentions is that the migration is the easy bit. Convincing four teams to stop forking the component is the actual work.
Textarea
Five places people are asked to write something — a support ticket, a product review, a job application, a social post and a creative brief.
Tell us what went wrong
A real engineer reads every ticket. The more specific you are, the fewer rounds of questions we will need.
How is it, six weeks on?
Reviews from people who actually bought the piece help everyone else choose well.
- Focus on the product, not the delivery
- No personal details or links
- Published within one working day
Why this role, and why now?
We are less interested in your CV than in what pulled you to this particular job. Three or four paragraphs is plenty.
Tell us about something you got wrong.
A project, a decision, a hire. What you learned matters more than the mistake itself.
Your answers are saved automatically. You can come back to this page from the link we emailed you.
We solved this by making the design system a dependency with a version number. Suddenly people cared about upgrades.
Onboarding redesign
What is not working today? Be specific — symptoms are more useful than diagnoses.
One measurable outcome. If you have three, pick the one you would defend in a board meeting.
Constraints, sacred cows, work already in flight.