Hello, I'm Todd

I’ve written this guide because I truly value diversity in backgrounds, thoughts, and opinions. This means that I understand the danger in assuming the way I do something is the “best” way; but rather, it's just what works best in the context of Todd.

Let this user guide serve as a cheat sheet to quickly build trust and understanding by clarifying how I work best. 

• For me, a successful Product Manager could also be called “Product Experience Advocate” as nothing in this world exists in a vacuum and a focus on advocating for a Product experience helps us to define success within the specific context a Product exists.  
• I believe a good Product Manager maintains a deep understanding and curiousity in how their Product is supporting stakeholders from day to day, as well as how it supports the overall business mission. 
• I prefer to define the success of specific projects before work is started, working with all stakeholders to ensure there is alignment on what problem’s we’re solving, why the solution solves this problem, and measurable ways to know how we achieved the outcomes we’re working towards.  
• Success is a practice of learning and getting better. We learn from failed and successful projects, so it’s important to consistently practice looking at our work to know what actions and processes support our goals and which of those slow us down.
• I believe it’s important to have a deep understanding of the existing issues and enhancement opportunities of my products to not only support the prioritization of tactical work, but to also add justification for strategic work that supports those outcomes.

• Urgent, Long Discussion: Phone, Video Call
• Urgent, Short Discussion: Chat/IM
• Non-Urgent, Long Discussion: Meeting w/Agenda
• Non-Urgent, Short Discussion: Chat/IM/Meeting w/Agenda