Thinking · Notes & ideas
Find the problem behind the request.
A useful direction connects what people need today with what the product needs to support next.
Look for the pattern.
The Job Details page had collected feature requests until the structure itself became difficult to use. Another button would not fix that. The opportunity was to rethink the framework, the hierarchy, and how information connects.
Keep the decision grounded.
Usage data, conversations with users, and feedback from onboarding teams helped reveal the recurring friction. That context gave the design a clearer purpose: reduce noise, surface useful information, and leave room for future workflows.