at Global Commons inc (3 years) • Product Manager, DevRel, Sales Engineer of Movable Type (original blogging software) at Six Apart KK (8.5years) • DevRel, Developer Success at Freee K.K (Japanese Unicorn, 3.5years) • CRE (Customer Reliablity Engnieer) at FLUX inc (current)
• Breaking changes will be adopted to the API Your Mission • Communicate with developers and get them to modify a huge number of systems and applications.
does not involve backward compatibility. • Breaking Change often causes external systems and applications to stop working, requiring third parties to modify their systems.
with the engineering team to sort out what the changes will be, how many changes will occur, and what types of changes they are. • You can't start a project without understanding what the changes are. • As the Developer Relation person, make sure you understand and sort out the changes.
the project Before 1 year (Nov-Dec 2019) Before 6months (May 2020) Before 5months (June 2020) Before 3 months (Jul-Aug 2020) Before 1month (Nov-Dec 2020) Month of Execution (Jan 2021) * Confirmed changes *Created the Schedule *Created the Communication plan * Published the release notes * Started to provide the new version of API *Communicated to external developers and stakeholders * Confirmed log data * Switched to the new version of API * Discontinue releasing the old version
one communication via developer’s site via Twitter send email to developers Sync internal stakeholders Sync over orgnaization investigate log data communicate developers privately Release notes News FAQ send private email discuss one by one communicate via sales team communicate via success team communicate via support team ready to track metrics with analytics team discuss with sales team about how to communicate
and the communication plan, it is time to coordinate with stakeholders both inside and outside.. • We have to continue to communicate based on our passion and beliefs as a Developer Relation person.
important thing is to "deliver the information to the developers who need it. • We asked every internal stakeholders within the company to help us contact all third parties and developers.
May Published News June Coordinate with internal members July, August Communicated via internal members to external developers and third parties December Final communication one by one before switching to specification
possible. • "Publishing release notes and blogs" is not enough to reach all developers. • We have to think, think, think, and execute, execute “How can I deliver information effectively to developers” • “Working with the teams” is essential.