The Art of Feature Delivery: Practical Tactics for Tech Leads and EMs
Owning and delivering a feature might seem like a standard responsibility for senior engineers and tech leads—but doing it exceptionally well is rarer than you'd think. This roundtable brings together seasoned leaders from Android and Flutter teams to discuss the often-overlooked mistakes that can derail feature development, even for experienced ICs and EMs. From poor documentation and unclear communication to lack of collaboration and hidden decision-making, we'll explore what not to do—and how to do better. Together, we’ll share stories, surface patterns, and identify habits that lead to smoother execution, stronger team dynamics, and better outcomes.
What’s one misstep you've seen (or made) when leading a feature that created avoidable friction or confusion?
How do you balance speed with documenting decisions and trade-offs—especially when timelines are tight?
Have you ever seen (or experienced) communication breakdowns because too much happened in DMs or side chats? How do you promote visibility without slowing down progress?
How do you encourage engineers to challenge each other’s solutions without creating tension or hierarchy in the team?
What strategies have worked for you to keep large features on track without micromanaging every detail?
Myths That May Be Holding You Back from Pursuing Engineering Leadership
When exploring leadership career paths, there might be some myths holding engineers back, some of which are completely baseless. My talk will cover such myths,
Myth number 1: I need to increase my visibility (the worst advice one can give to someone to explore the leadership career path is ‘increase your visibility’) I will explain with examples how it’s an absolute myth
Myth number 2: Only extroverts can succeed as managers (I will explain what are main areas of success for a manager and how being extrovert isn’t one of them)
Myth number 3: I’m expected to never say no (I will explain how saying No to requests from outside the time can help a great deal in success of a manager and how saying yes all the time can be dangerous)
Myth number 4: I’ll spend most of my time in meetings (I will explain how this role can influence a lot of changes on ways working in / out of a team including the number of meetings)
[Bonus] Self Doubt: I’ll be viewed as technically less competent (I will challenge this notion with examples)
Key takeaways and learning points
Deeper understanding on what actually is a job of an engineering manager, what are the key skills required for the role, what are they key areas that will make the person successful
Experience level with the topic
Expert, I am head of engineering in my current role and hence I have several years of experience delivering features and leading teams.
In addition to my experience, I believe that my perspective as a woman can contribute meaningfully to this topic. I will do this talk in the Droidcon Berlin this year as well.
Don'ts of Feature Ownership and Development
It seems fairly easy to lead a feature however only a few can do it really well. There are a lot of things that people can miss even in something that is the core task of their role. During my many years of leading Android teams, I have noticed what are the smallest things that make a project journey smooth as silk. My talk will cover these areas,
1. Don’t overlook the importance of understanding the problem (here i will explain the must haves)
2. Don't skip documenting the solution extensively - even the tiniest detail (here i will emphasis on what are the must haves for documentation)
3. Don’t hold back on providing alternatives or disagreeing with other’s solutions
4. Avoid private chats for solution talks; ensure visibility by using shared channels (i will explain examples of what kind of message is a fit for DM and what will be better for common channel)
5. Don’t act superior - treat your engineering peers as equals (here i will share example of what can be taken as condescending)
6. Don’t lose sight of the required tasks and their target dates
I will focus on don’ts and provide solutions to each point written above with examples.
Key takeaways and learning points
What to avoid while leading a feature, it can be ownership of a small feature or a huge initiative that go on for many months
Experience level with the topic
Expert, I am head of engineering in my current role and hence I have several years of experience delivering features and leading teams.
In addition to my experience, I believe that my perspective as a woman can contribute meaningfully to this topic. I will do this talk in the Droidcon Berlin this year as well.
Please note that Sessionize is not responsible for the accuracy or validity of the data provided by speakers. If you suspect this profile to be fake or spam, please let us know.
Jump to top