As in many young companies, development teams at Instana constantly released great products and feature advancements driven by inherent hero culture, but struggled with identifying bottlenecks. As the team grew, a more stable way of working was needed.
Distributed development teams responsible for different services and spread across multiple time zones do not necessarily have to work in the exact same way as on-site teams. Each team has different priorities and needs to work in a way that facilitates their current work mode. At Instana, we introduced Kanban and leveraged it to gain better visibility into the actual work being done and where bottlenecks occurred.
This talk provides attendees with insights into how engineering teams at Instana transitioned to a Kanban-based work model and how each team took responsibility for their own service quality. We'll discuss challenges, advantages and even disadvantages of our current work model and share the lessons we learned. We hope this will help other organizations struggling with similar issues.
You’ve probably written a hundred abstracts in your day, but have you come up with a template that really seems to resonate? Go back through your past webinar inventory and see what events produced the most registrants. Sure – this will vary by topic but what got their attention initially was the description you wrote.
Paint a mental image of the benefits of attending your webinar. Often times this can be summarized in the title of your event. Your prospects may not even make it to the body of the message, so get your point across immediately. Capture their attention, pique their interest, and push them towards the desired action (i.e. signing up for your event). You have to make them focus and you have to do it fast. Using an active voice and bullet points is great way to do this.
Always add key takeaways. Something like this....In this session, you’ll learn about: