INTERFACE, by apidays - Convincing at scale by Marcelo Araujo & David Halsband, Bosch
•Descargar como PPTX, PDF•
0 recomendaciones•87 vistas
INTERFACE, by apidays 2021 - It’s APIs all the way down June 30, July 1 & 2, 2021 Convincing at scale Marcelo Araujo, Lead API Center for Enablement at Bosch USA & David Halsband, Enterprise Architect IoT and Digitalization at Bosch
Recomendados
Recomendados
Más contenido relacionado
La actualidad más candente
La actualidad más candente (20)
Similar a INTERFACE, by apidays - Convincing at scale by Marcelo Araujo & David Halsband, Bosch
Similar a INTERFACE, by apidays - Convincing at scale by Marcelo Araujo & David Halsband, Bosch (20)
Más de apidays
Más de apidays (20)
Último
Último (20)
INTERFACE, by apidays - Convincing at scale by Marcelo Araujo & David Halsband, Bosch
- 1. Convincing at scale Marcelo Araujo Georg Grütter David Halsband Making the case for APIs 53 years after-the- fact 1
- 2. Bosch.IO - Georg Grütter | 2021-06-17 © Robert Bosch GmbH 2021. All rights reserved, also regarding any disposal, exploitation, reproduction, editing, distribution, as well as in the event of application for industrial property rights 2 Bosch.IO - Georg Grütter | 2021-06-17 © Robert Bosch GmbH 2021. All rights reserved, also regarding any disposal, exploitation, reproduction, editing, distribution, as well as in the event of application for industrial property rights 120 R&D Locations 400,000 Associates 59,000 in R&D
- 3. API Days 2021 – Convincing at Scale © Robert Bosch GmbH 2021. All rights reserved, also regarding any disposal, exploitation, reproduction, editing, distribution, as well as in the event of application for industrial property rights Do we still need to talk about APIs? 3
- 4. API Days 2021 – Convincing at Scale © Robert Bosch GmbH 2021. All rights reserved, also regarding any disposal, exploitation, reproduction, editing, distribution, as well as in the event of application for industrial property rights Img src: http://computationalculture.net/heterogeneous-software-engineering-garmisch-1968-microsoft-vista-and-a-methodology-for-software-studies/ 1968 NATO software Engineering conference 4
- 5. API Days 2021 – Convincing at Scale © Robert Bosch GmbH 2021. All rights reserved, also regarding any disposal, exploitation, reproduction, editing, distribution, as well as in the event of application for industrial property rights Image source: Deposit photos / Free License https://depositphotos.com/110638182/stock-photo-valuable-golden-egg-for-leadership.html 5
- 6. API Days 2021 – Convincing at Scale © Robert Bosch GmbH 2021. All rights reserved, also regarding any disposal, exploitation, reproduction, editing, distribution, as well as in the event of application for industrial property rights 2015 2021 https://hbr.org/2021/04/apis-arent-just-for-tech- companies https://hbr.org/2015/01/the-strategic-value-of-apis 6
- 7. API Days 2021 – Convincing at Scale © Robert Bosch GmbH 2021. All rights reserved, also regarding any disposal, exploitation, reproduction, editing, distribution, as well as in the event of application for industrial property rights 7
- 8. API Days 2021 – Convincing at Scale © Robert Bosch GmbH 2021. All rights reserved, also regarding any disposal, exploitation, reproduction, editing, distribution, as well as in the event of application for industrial property rights Why isn’t its value leveraged by all? 8
- 9. API Days 2021 – Convincing at Scale © Robert Bosch GmbH 2021. All rights reserved, also regarding any disposal, exploitation, reproduction, editing, distribution, as well as in the event of application for industrial property rights Hype Cycle 9
- 10. API Days 2021 – Convincing at Scale © Robert Bosch GmbH 2021. All rights reserved, also regarding any disposal, exploitation, reproduction, editing, distribution, as well as in the event of application for industrial property rights Gartner Hype Cycle 10
- 11. API Days 2021 – Convincing at Scale © Robert Bosch GmbH 2021. All rights reserved, also regarding any disposal, exploitation, reproduction, editing, distribution, as well as in the event of application for industrial property rights Gartner Hype Cycle 11
- 12. API Days 2021 – Convincing at Scale © Robert Bosch GmbH 2021. All rights reserved, also regarding any disposal, exploitation, reproduction, editing, distribution, as well as in the event of application for industrial property rights “By 2021, 25% of organizations with public APIs will have discontinued or rebooted their public API strategy” Mark O’Neil https://www.linkedin.com/pulse/end-beginning-api-economy-mark-o-neill 12
- 13. API Days 2021 – Convincing at Scale © Robert Bosch GmbH 2021. All rights reserved, also regarding any disposal, exploitation, reproduction, editing, distribution, as well as in the event of application for industrial property rights Gartner Hype Cycle 13
- 14. API Days 2021 – Convincing at Scale © Robert Bosch GmbH 2021. All rights reserved, also regarding any disposal, exploitation, reproduction, editing, distribution, as well as in the event of application for industrial property rights Convincing at scale 14
- 15. API Days 2021 – Convincing at Scale © Robert Bosch GmbH 2021. All rights reserved, also regarding any disposal, exploitation, reproduction, editing, distribution, as well as in the event of application for industrial property rights Establish a brand 1 15
- 16. API Days 2021 – Convincing at Scale © Robert Bosch GmbH 2021. All rights reserved, also regarding any disposal, exploitation, reproduction, editing, distribution, as well as in the event of application for industrial property rights Have incentives 2 16
- 17. API Days 2021 – Convincing at Scale © Robert Bosch GmbH 2021. All rights reserved, also regarding any disposal, exploitation, reproduction, editing, distribution, as well as in the event of application for industrial property rights Provide guidance 3 17
- 18. API Days 2021 – Convincing at Scale © Robert Bosch GmbH 2021. All rights reserved, also regarding any disposal, exploitation, reproduction, editing, distribution, as well as in the event of application for industrial property rights Promote a lighthouse project 4 18
- 19. API Days 2021 – Convincing at Scale © Robert Bosch GmbH 2021. All rights reserved, also regarding any disposal, exploitation, reproduction, editing, distribution, as well as in the event of application for industrial property rights Cross-pollination 5 19
- 20. API Days 2021 – Convincing at Scale © Robert Bosch GmbH 2021. All rights reserved, also regarding any disposal, exploitation, reproduction, editing, distribution, as well as in the event of application for industrial property rights Community driven governance 6 20
- 21. API Days 2021 – Convincing at Scale © Robert Bosch GmbH 2021. All rights reserved, also regarding any disposal, exploitation, reproduction, editing, distribution, as well as in the event of application for industrial property rights Connect Supply with Demand 7 21
- 22. API Days 2021 – Convincing at Scale © Robert Bosch GmbH 2021. All rights reserved, also regarding any disposal, exploitation, reproduction, editing, distribution, as well as in the event of application for industrial property rights Developer portal 8 22
- 23. API Days 2021 – Convincing at Scale © Robert Bosch GmbH 2021. All rights reserved, also regarding any disposal, exploitation, reproduction, editing, distribution, as well as in the event of application for industrial property rights 23 Why we still need to convince?
- 24. API Days 2021 – Convincing at Scale © Robert Bosch GmbH 2021. All rights reserved, also regarding any disposal, exploitation, reproduction, editing, distribution, as well as in the event of application for industrial property rights Thank you! 24
- 25. API Days 2021 – Convincing at Scale © Robert Bosch GmbH 2021. All rights reserved, also regarding any disposal, exploitation, reproduction, editing, distribution, as well as in the event of application for industrial property rights Q&A 25 Marcelo - @apiglue
Notas del editor
- Hello everyone and welcome. My name is Marcelo, im very excited to be here today and together with my colleague and co-host David, which is here with us, and Georg, who unfortunately couldn’t join us today, we will talk about approaches we believe can be used to boost your api program. But more of that in a second. Let me begin giving you a bit of background of Bosch
- We’re a roughly 400.000 employee global company and we are organized into 4 business sectors: Sector of Mobility solutions: Where we are one of the leading automotive suppliers globally, with an extensive portfolio of hardware, electronics, systems solutions, software, and services for nearly every type of vehicle and powertrain. Sector of Industrial technologies: Where we are a leading supplier of software, systems, and components for a wide variety of manufacturing and logistics applications. Sector of Energy and Building Technology: we have a broad portfolio of intelligent, connected, and efficiency-enhancing products, systems, and services for residential and commercial properties as well as business management solutions. Sector of Consumer goods: With our home appliance and power tools businesses, Bosch supplies smart, connected, and resource-conserving products and services for the home and garden, as well as for professional users in trade and industry.
- Alright, so the question really is: 2021, do we really need to talk about the importance of APIs?
- The term has been around since half a century now. Can you believe it? It was mentioned during 1968 nato’s sw eng conference and on the “Data structures and techniques for remote computer graphics” paper of the American Federation of Information Processing Societies. As a fun fact, on this paper, foundational API concepts like Flexibility, independence, reuse were already understood among the software engineering community.
- While is probably safe to say that most software developers tend to understand the value of an APIs early on, it seems that 53 years later there are still a lot of missed business opportunities that flew and are actually flying under the radar of companies of all industries. And by opportunities, I don’t necessarily mean those unicorn pay-per-use APIs. Opportunities also includes using APIs to increase process efficiency, reduce cost through automation and simplify access to data. Why is that, I wonder. Why are those opportunities aren’t being fully taken advantage of?
- Take Harvard Business Review, for example. They keep releasing articles about the importance of APIs. The one on left side, which date back to 2015, explains the strategic value of APIs and how they are the windows to new ecosystem and revenue streams. Fast forward to 2021, HBR published another article highlighting again, the importance of APIs, specially emphasizing they aren’t just for tech companies.
- And that’s just to name one publisher. == CLICK == Lots of well other respected business publishers already addressed this very same topic frequently, since at least 10 years.
- Obviously, the fact APIs “add value”, its not a new thing. It have been covered extensively in the media – not to mention the fact that, as all you are aware of, APIs are today, directly or indirectly, embedded in almost everyone’s life. Why we, and I say this as “we, the whole API community” still even need to convince that API is something that worth investing in? == PAUSE == 3s Don’t we have enough api-powered success cases? == PAUSE == 3s it turns out there’s a model that *might* help explain.
- Its from Gartner, and its called the “Hype Cycle” that represent the maturity, adoption, and social application of specific technologies.
- This hype cycle have 5 key phases, starting on a potential technology breakthrough, to a peak of expectations, down to disillusionment, and finally mainstream adoption I want to direct your attention to the phase called the ==CLICK== “Trough of disillusionment” Typically, a trend ends up here after the technology in question failed to deliver to its original promises.
- And not by coincidence, “Trough of disillusionment” come right after the ==CLICK== “Peak of Inflated Expectations”. Maybe that massive publicity we saw earlier, could’ve created an “API bubble” which burst into disappointment to several companies?
- To further support that fact, Gartner’s Analyst Mark O’Neil said in an article about the state of the API economy: ”…Web APIs have been going down the Hype Cycle "Trough of Disillusionment" for some time now[…]. This is because too many organizations have published APIs without forethought about who the users will be, or what value chains they will enable. “ We’d love to hear from you in the Q&A if you experienced the same bubble, because we are no exception to that. But this team’s passion for APIs and our belief that they are a cornerstone of our transformation gave us the fuel to go for the…
- …the slope of enlightenment. ==CLICK== (DAVID SAYS) But in order to start climbing, we would need a plan on how to… (DAVID NEXT)
- Convince at scale. That is, create new ideas that would help us get the giant organization that we are on, on-board, towards one direction. We came up with 8 approaches that worked for us, which we would like to share with you now
- (DAVID) A good start for an API program is to establish a brand and to give your activity a name. We created a logo ==CLICK== This is ours: API1st. We printed stickers, we made videos and did some internal marketing. In our case we noticed, that many people associate different things with that term API1st. For us it is a set of principles, that you should keep in mind, when you are developing an API or designing a system or a product that will offer an API. And it also describes a target state and a new mindset. Very simple. Now the tricky part is to explain why API1st matters so much. We did that by making API1st part of our Corporate Digital Strategy at Bosch. In there, we explained the strategic importance of APIs and the value for our business. It is important that managers and executives can understand this link so they can relay the message that APIs are not only a fancy technology, but also the foundation of digital value creation. The brand and the logo helped us, that our colleagues can recognize, what we are doing and that the term API1st is understood. And it also makes it exciting to join and attractive to be part of the game. (MARCELO NEXT)
- (MARCELO) Number 2 – Have incentives Let me start saying that incentives can be super obvious in some cases, for example, in the situation that your public APIs will generate direct revenue. But other situations, like when dealing with internal APIs, the story is a bit different. There will always be a demand for an API, whose underlying process owner is not part of your IT team nor familiar on what entails to become an API provider. API ownership cannot and should not be someone's “side gig”. As I usually say, becoming an API provider is like going from making your own lunch to opening a restaurant. You can’t accommodate that easily on top of your daily duties without support from the organization. What incentives you should provide for them to become an API provider? Apart from common approaches of making “ownership” an organizational goal, you could think in creating an Internal API economy, which would allow API ownership to be attractive. The result of this approach can generate high quality APIs, which will serve as incentives for your API consumers to use it.
- (MARCELO) Number 3 – provide guidance Like we just discussed, when executing a company-wide API program, be cognizant that not everyone will be familiar on what it takes to become and API provider. Many will have questions like: How do I deal with data protection (i.e. GDPR), What legal aspects my API should abide to? Which compliance process should I apply? In addition to the incentives we just talked, Its important to have in place people and documentation that can help guide them on how to become a successful API provider. This guidance can be provided in many dimensions, for example: Leveraging organizational setups like an API center for enablement providing consultancy or even building APIs for your organization An API style guide and other guidelines, blueprints and best practices An even a concierge service for publishing APIs – They should be able to help you navigate your organizational complexity (DAVID NEXT)
- (DAVID) - Number 4 – Promote a lighthouse project We recognized, that it is impossible to convince the whole organization at once about APIs. It is common for teams to wait for the result of other teams before starting themselves. Either because of being afraid of failure or not having a clear idea what exactly it would look like. For us it was a better idea to focus on those, who are willing to make the first move together with us. Therefore, we created a little contest, where you could apply with a project, that we would support with our expertise for free. The criteria we applied to select our lighthouse project, where: it should be possible to show success within 6 months the API should not be a gimmick within the project, but very business relevant it should be run by a motivated team with the willingness to share learnings We selected a cool project and a team, that shared the same passion for APIs. Together we are designing a customer-facing product, helping them to demonstrate the value of APIs to the rest of the organization. To become a lighthouse , you should promote the heck out of it and make sure that it gets all the attention it deserves. Other teams hopefully will be eager to follow suit, once you can show them how successful your lighthouse was. You need those early success stories to convince more people in the organization. Especially when you talk to management and ask for budget, it is crucial to have proven examples. (MARCELO NEXT)
- (MARCELO) Number 5 – Cross-pollination This works well in conjunction with the number 3 (provide guidance), where I mentioned that having dedicated people, best practices and strategies are super important, but those also have limitations when it comes to disseminating knowledge. In most cases, it won't justify to scale a team to address an entire organization initiative. So, to complement that, think about establishing communities of practices. Having people outside the API core team interacting and helping other API fellows, will help to scale the knowledge faster and more consistently. (DAVID NEXT)
- (DAVID) - Number 6 – Community driven governance We consciously decided against a traditional, top down governance approach with strict controls and sanctions. Instead we have chosen to follow a community driven approach, in which our API experts are empowered to create and to evolve API governance. We believe this will result in a more adequate and more sustainable governance. Adequate meaning: Governance is defined by those who have to deal with it later. If I have to eat my own dogfood, I better try to make it tasty. And sustainability has two aspects. 1. I eliminate resistance and the "not invented here syndrome" by putting those who have to live with it in the driver's seat. 2. Rather than engaging in fingerpointing to a central governance unit in case the governance needs to be adapted due to changes in technology/business, the responsibility to keep governance up to date and helpful rests with the community. (DAVID NEXT)
- (DAVID) - Number 7 – Have a way to connect supply with demand Like in every economy, there are these two main drivers, supply and demand. In this case, supply are the APIs that your organization is offering, and demand are those APIs that others would like to consume. You can probably imagine that in large organization, connecting both sides, isn’t a trivial task. So, its very important that you make your APIs discoverable and understand which APIs are needed by the organization. In our case, we introduced an API wish list, where everyone can request a missing API and others can vote on them. Connecting helps you flourish your API economy. (MARCELO NEXT)
- (MARCELO) Last but not least, Number 8 – Developer portal Often overlooked, a developer portal should Ideally play a much larger role other than serving just as a documentation repository. For example, is a great place to connect your supply with demand, as we just learned. In addition to host documentation that must give the consumer every information they need to start using an API, they also could provide: API wish list – Have a way to people request new apis, in case they don’t find what they’re looking for. Case Studies and Examples – highlighting applications that have been built using your API. Easy Onboarding – APIs rarely gain adoption if you make it difficult to get started. Easy onboarding, from self-registration to a guided tour will help developers overcome the challenges to adopting a new API. Operational Status – Is your API available or temporarily down? A simple status page that reflects your API’s availability will help to inform developers and operations staff that see increased errors in their applications. ===(DAVID SAYS) Those were the 8 approaches we wanted to share with you, (DAVID NEXT)
- (DAVID) But coming back to the question “Why we still need to convince?” Because we are dealing with change. Possibly large-scale change. Cultural Change, Process Change, Technology Change. We are asking our organizations to change the way we communicate, to change the way we collaborate, to change the way we do business. Its just natural that this transition takes time. And while this “cultural change” is not an easy thing to do, it is definitely the right thing to do. == PAUSE == We hope that one or more of our approaches can also help you through YOUR change, as it is helping with ours. And don’t give up - fellow evangelists. Don’t give up - Its worth it.
- We know there are some amazing speakers in the parallel sessions so, thank you so much for your time today. Thanks for being here. Now, we do have a couple of minutes for Q&A.
- And we’ll do our best to answer any questions you might have, and also feel free to use this time just to share your experiences about what we’ve discussed.