Mary Thengvall

Mary Thengvall Mary Thengvall Mary Thengvall Mary Thengvall Mary Thengvall

Director, Developer Relations Director, Developer Relations Director, Developer Relations Director, Developer Relations Director, Developer Relations @ Camunda Camunda Camunda Camunda Camunda

Mary Thengvall is a connector of people at heart, personally and professionally. She loves digging into the strategy of how to build and foster developer communities and has been doing so for over 10 years. Mary is the Director of Developer Relations at Camunda, an open source process automation platform. She's the author of the first book on Developer Relations: The Business Value of Developer Relations (© 2018, Apress). Mary Thengvall is a connector of people at heart, personally and professionally. She loves digging into the strategy of how to build and foster developer communities and has been doing so for over 10 years. Mary is the Director of Developer Relations at Camunda, an open source process automation platform. She's the author of the first book on Developer Relations: The Business Value of Developer Relations (© 2018, Apress). Mary Thengvall is a connector of people at heart, personally and professionally. She loves digging into the strategy of how to build and foster developer communities and has been doing so for over 10 years. Mary is the Director of Developer Relations at Camunda, an open source process automation platform. She's the author of the first book on Developer Relations: The Business Value of Developer Relations (© 2018, Apress). Mary Thengvall is a connector of people at heart, personally and professionally. She loves digging into the strategy of how to build and foster developer communities and has been doing so for over 10 years. Mary is the Director of Developer Relations at Camunda, an open source process automation platform. She's the author of the first book on Developer Relations: The Business Value of Developer Relations (© 2018, Apress). Mary Thengvall is a connector of people at heart, personally and professionally. She loves digging into the strategy of how to build and foster developer communities and has been doing so for over 10 years. Mary is the Director of Developer Relations at Camunda, an open source process automation platform. She's the author of the first book on Developer Relations: The Business Value of Developer Relations (© 2018, Apress).

Video

Slide

First, Understand the Company Goals

Session information

First, Understand the Company Goals First, Understand the Company Goals First, Understand the Company Goals First, Understand the Company Goals First, Understand the Company Goals

🗣 english 🕘 02:15 〜 02:45 UTC at China
"What is the main goal of a DevRel team?" is a question I've heard for years, and every time, the answer starts with "well... it depends!" What if I told you that the main goal of DevRel -- no matter what company you're at -- is to support the company's empowerment of the developer community? From this understanding comes awareness (speaking at conferences or writing up best practices), enablement (getting started guides and tutorials), and engagement (making community members feel welcome and included). From this singular goal, you can more easily see where you fit into the broader tapestry of your company's goals and objectives for the weeks, months, and years ahead. The end result? A stable Developer Relations team that can easily point to the value they're bringing to the community as well as the company. "What is the main goal of a DevRel team?" is a question I've heard for years, and every time, the answer starts with "well... it depends!" What if I told you that the main goal of DevRel -- no matter what company you're at -- is to support the company's empowerment of the developer community? From this understanding comes awareness (speaking at conferences or writing up best practices), enablement (getting started guides and tutorials), and engagement (making community members feel welcome and included). From this singular goal, you can more easily see where you fit into the broader tapestry of your company's goals and objectives for the weeks, months, and years ahead. The end result? A stable Developer Relations team that can easily point to the value they're bringing to the community as well as the company. "What is the main goal of a DevRel team?" is a question I've heard for years, and every time, the answer starts with "well... it depends!" What if I told you that the main goal of DevRel -- no matter what company you're at -- is to support the company's empowerment of the developer community? From this understanding comes awareness (speaking at conferences or writing up best practices), enablement (getting started guides and tutorials), and engagement (making community members feel welcome and included). From this singular goal, you can more easily see where you fit into the broader tapestry of your company's goals and objectives for the weeks, months, and years ahead. The end result? A stable Developer Relations team that can easily point to the value they're bringing to the community as well as the company. "What is the main goal of a DevRel team?" is a question I've heard for years, and every time, the answer starts with "well... it depends!" What if I told you that the main goal of DevRel -- no matter what company you're at -- is to support the company's empowerment of the developer community? From this understanding comes awareness (speaking at conferences or writing up best practices), enablement (getting started guides and tutorials), and engagement (making community members feel welcome and included). From this singular goal, you can more easily see where you fit into the broader tapestry of your company's goals and objectives for the weeks, months, and years ahead. The end result? A stable Developer Relations team that can easily point to the value they're bringing to the community as well as the company. "What is the main goal of a DevRel team?" is a question I've heard for years, and every time, the answer starts with "well... it depends!" What if I told you that the main goal of DevRel -- no matter what company you're at -- is to support the company's empowerment of the developer community? From this understanding comes awareness (speaking at conferences or writing up best practices), enablement (getting started guides and tutorials), and engagement (making community members feel welcome and included). From this singular goal, you can more easily see where you fit into the broader tapestry of your company's goals and objectives for the weeks, months, and years ahead. The end result? A stable Developer Relations team that can easily point to the value they're bringing to the community as well as the company.