Kurtis Kemple’s Post

View profile for Kurtis Kemple, graphic

Senior Director of Developer Relations | Driving Platform Growth | Quantifying Developer Success

As DevRel leaders, we're constantly seeking ways to maximize our impact and streamline our operations. In my latest blog post, I dive into how systems thinking and recognizing invisible work can improve your DevRel strategy. Key takeaways: 📊 Improve reporting by capturing the full scope of DevRel impact 🤝 Enhance team understanding and clarify roles 🪜 Develop more aligned career ladders ⚙️ Implement practical strategies for visibility and efficiency I share insights from our experience at Slack, including our tiered approach to customer enablement and how it's shaped our team structure. Whether you're a seasoned DevRel professional or new to the field, this post offers valuable perspectives on optimizing your team's potential. Read the full article here: https://lnkd.in/eueuk_6r What strategies have you found effective in your DevRel efforts? Share your thoughts in the comments! #DevRel #SystemsThinking #TeamManagement #CareerDevelopment

Systems Thinking and Invisible Work: Bringing Clarity to DevRel

Systems Thinking and Invisible Work: Bringing Clarity to DevRel

kurtiskemple.com

Taylor Singletary

Head of developer relations at Retool

2mo

Was just recently talking about how developer relations is more of a system than a team and with a system... the purpose of the system is what it does -- including the side effects, maybe even mostly the side effects. When you recognize this you start making project work systems work... you can use it to meet a few metrics you're after sure but most of the true value is in the immeasurable side effects that are just as much a purpose of the system as the things done with intent.

To view or add a comment, sign in

Explore topics