The most effective first step to improve developer experience (DevEx) is not building automation or buying tools. Instead, conduct a 'listening tour' with developers about their daily friction. This uncovers high-impact, low-lift opportunities that premature solutions often miss.

Instead of fielding endless private Slack DMs, create a public intake channel for all requests. This system allows the entire team to see the volume of work, enabling better triage and load balancing, while also building empathy with stakeholders who can now visualize the team's true workload.

An engineering firm initially siloed access to departmental folders. They found that when an engineer's input was needed on a sales quote or marketing material, the project would stall while waiting for IT to grant access. Giving broad access by default removes this friction and speeds up cross-functional work.

Field engineers can bypass documentation limitations by querying the entire codebase with AI tools like Claude Code. This provides detailed, step-by-step answers that public docs lack, directly addressing complex customer problems and reducing reliance on the engineering team.

To foster genuine advocacy with technical audiences, you must go beyond swag. Grant them a sense of ownership by incorporating their ideas into the roadmap and providing APIs to extend the product. Then, make it incredibly easy for them to share their creations and be sure to celebrate their contributions publicly.

To get product management buy-in for technical initiatives like refactoring or scaling, engineering leadership is responsible for translating the work into clear business or customer value. Instead of just stating the technical need, explain how it enables faster feature development or access to a larger customer base.

The debate between being product-led vs. sales-led is a false dichotomy that creates friction. Instead, frame all functions as fundamentally 'customer-driven.' This reframing encourages product teams to view sales requests not as distractions, but as valuable, direct insights into customer needs.

To get a major initiative approved, don't just pitch the vision. Interview key decision-makers beforehand and ask for every possible objection. Then, build your pitch around a mitigation plan for each concern, removing every reason for them to say 'no' before you even formally present.

Stop treating colleagues like an API where you expect a specific output for a given input. Instead, acknowledge their constraints ("I know you have a busy roadmap...") and frame your need as a collaborative problem to solve together. This builds goodwill and yields better results.