Profile
Reid Butler

Reid Butler

Director of Product Management, Cisco

Content

Reid Butler
Cisco Director of Product ManagementDecember 19
A super common question! Traditionally the term "product manager" can often mean different things depending on the size of the company, the product's stage, and sometimes the overall market segment. I often times bucket them into these core groups: 1. Technical Product Managers (TPM): These PMs work closely with engineering teams on more technical products, thinks like API driven products where the end "customer" is technical in nature. For these roles, you will need a deeper level of technical expertise and the ability to understand the technical aspects of your customers needs. 2. B2C (Business to Consumer) Product Managers: In a consumer-facing environment—like mobile apps, e-commerce platforms, media consumption products — I find that PMs often emphasize UX and product design (along with core PM responsibilities). One of the key areas that this group focuses on is leveraging a typically broader/larger customer base to do things like A/B testing, and quick iteration on product designs to validate assumptions and feature value. 3. B2B (Business to Business) Enterprise Product Managers: These enterprise PMs focus on delivering products that solve businesses' complex problems. I spent a lot of my career here and this type of PM spends a lot of time on sales enablement, strategic account engagement, and roadmap management. Given that most B2B solutions have a longer sales cycle, their relationship with sales is key to success. Depending on the size of the organization, this type of PM also focuses a lot on the financial side of the product. 4. Infrastructure Product Managers: These PMs (sometimes internally facing only) focus on building components that other teams and products rely on, oftentimes within an organization. For them, the GTM isn't as relevant but they need to understand and balance things like scale, interoperability, and business alignment. Figuring Out Your Best Fit: 1. What are your Interests: Consider things like Do you enjoy getting into the weeds on technical discussions? Do you more get energized by user research and design? Do you geek out over analytical data and love looking at usage metrics to drive feature development? Each type of role has a different focus, so find the things that excite you. 2. Consider the Environment Do you want to reach a huge market of customers and iterate on minor feature developments and enhancements? Or do you want to work closely with larger business customers and develop a deeper understanding of their problems and how your product can evolve to meet those specific needs? No right or wrong answer, just what gets you pumped up each day. Remember, it’s about aligning your career desires, your core strengths, and the types of challenges that get you fired up to solve each day. We are problem solvers, so what types of problems do you love solving and how do you like solving them? Many PMs start in one area and end up in another. All the roles share a common framework of ensuring we are delivering business value for our organization and delighting our customers with innovative and useful solutions to problems they either have or don't even realize they have yet.
...Read More
181 Views
Reid Butler
Cisco Director of Product ManagementDecember 19
When you’re working at an early-stage startup, I know it can feel like every conversation, Slack message, or email thread throws another item on your plate. It’s totally normal to feel overwhelmed because there is always more work than can be done by a PM. To help manage this, here are a few strategies and tips I use: 1. Define Clear Priorities and Communicate Them: Define the priorities for you and your team in terms of areas of focus. What are the most important things that will have the biggest impact on your product and your product success right now? For example, if you're at the design phase of a future release, you would prioritize things like user experience research, customer feedback, focus groups, etc. Be ruthless with your priorities, define them, and stick to them. Early in my career, I would get distracted by items that weren’t critical at that moment and later regret the distraction. The second part of defining priorities is communicating those. When your team and your stakeholders understand what your area is a focus is, it's easier to manage those incomings and set expectations. 2. Batch Your Interruptions: In a startup, the product manager is often the jack of all trades. This is a double-edged sword as being the focal point of many conversations allows you to drive the product strategy and execution with a greater degree of confidence and visibility, but it comes at a cost since everybody looks to us for every type of question. To help manage this, I typically carve out a block of time every day to respond to non-critical interruptions. Reserving a block of time either at the beginning or the end of the day allows me to defer those interruptions and knock them out without disrupting my flow. Context switching to handle incoming interruptions comes at a significant cost to your focus....so minimize that. 3. Empower the Team Around You and Defer: Typically with a small product management team, it's not possible to handle all of the incomings all of the time. Defer what you can to either other members of your team or a subject matter expert in another team. Don't be afraid to suggest speaking with somebody else to get the answer that they need. It's hard to let go sometimes, but protecting your focus is critical to being successful as a product manager. 4. Don't Be Afraid of No: Your time and capacity is valuable for your organization. Don't be afraid to say no to incoming interruptions in order to preserve your focus. It's not a black-and-white answer that applies to everything, but you need to use your best judgment and be comfortable, saying no to incoming asks and requests if it doesn't align with your priorities or won't help you drive product success. Be honest when you say no to something and be open to explaining why you are saying no. You never want to be the black hole of incoming requests where customers and stakeholders feel you don't respond....so always better to respond with a no vs ignoring and never responding.
...Read More
167 Views
Reid Butler
Cisco Director of Product ManagementDecember 19
The transition from a Sr Product Manager role to a director level usually focuses on developing your strategic thinking, influencing others across the organization, and guiding larger portfolio decisions. In other words, you’ll need to grow from an execution-based mindset to that of one centered on longer-term vision, team leadership, and effective decision-making (at scale). In my experience, these are the key areas that one should focus on. Skill Sets to Develop: 1. Strategic Vision & Storytelling: Climbing up the ladder isn’t just about managing more product roadmaps; it’s about defining the strategy and market direction, gaining a deeper understanding of the business strategy and how it relates to long-term execution plans and anticipating future market needs. A key bit of being at a higher level of telling that story and connecting those dots for others. Be good at explaining what the strategy is and why it's the right path for your organization. If you can't bring people along the journey, you will never get their full support. 2. Stakeholder Management: The higher you go, the more internal and external stakeholder management you will have. In lower levels that's more at a feature level management, but at a Director level, it's more about strategy implications and trade-offs with your stakeholders. 3. Leadership & Talent Development: Typically at the Director level or above is managing a team of Product Managers. For me, I have been managing Product Mgrs for nearly a decade and find it one of the most rewarding parts of the role. Growing a team of strong product thinkers and empowering them to execute efficiently is a huge part of moving up that corporate ladder. 4. Process Process Process As you move up, you need to ensure your team has the tools and processes in place to support them. You are less in the weeds each day and thus have to ensure that you have enabled them with a framework to follow that will make them successful in their careers and drive your product forward. However, I despise process for the sake of process (a common issue at larger organizations). Be willing to challenge a process that isn't adding value and ensure that what you drive provides your team the room to grow. I like to think of it as guardrails for my team. I don't tell them specifically what to do and a playbook/process to follow letter by letter. I provide them with guidance and point them down the right path with some guardrails to ensure they don't make a left when they should be going right. While I drive the overall process, I always remember that "just cause it wasn't done exactly how I would do it doesn't mean it wasn't done right."
...Read More
161 Views
Reid Butler
Cisco Director of Product ManagementDecember 19
Collaborating with Product Marketing is a key part of any product's success. In smaller teams/companies, that role can fall on to the Product Manager directly, whereas at bigger organizations that is a more dedicated role. I am fortunate now at Cisco to have access to some of the best product marketing resources in the business. The work that we do together from product strategy, execution planning, and external marketing helps ensure our business objectives are met and made visible within our specific market. We work closely throughout the GTM process and fostering this relationship is one of the key components to a solid product launch.
...Read More
161 Views
Reid Butler
Cisco Director of Product ManagementDecember 19
Of course they do! It's always a balance between those two sides. Mixing personal contributions with coaching other product managers can create tension if you’re not mindful. Setting clear boundaries around your schedule, defining what success looks like for both you and your team, and communicating these goals openly helps manage these two aspects. Things to Think About 1. Dedicated Coaching Time: I try and dedicate time each week to ensure my team is getting what they need and that I am providing them the opportunities to grow and gain exposure (to new skills, new teams, etc). If the team feels disconnected from their leadership, it's difficult to motivate them and keep them moving forward. 2. Defining Ownership: Whenever possible, I clarify what parts of the product I’m responsible for and what the team needs to own. When PMs clearly know what’s theirs to drive, it reduces the urge for me to dive in and micromanage. We play to our strengths, which allows me to contribute where I add unique value (eg: shaping high-level strategy or unblocking critical issues) while allowing each team member to do the same in their areas. 3. Regular Reflection: Every week and month, I reflect on where I’ve been spending my time. Did I neglect my direct product work because I was too hands-on with the team? Then I need to adjust next week. It's a constant balancing act. As I said, I work to carve out space, define ownership and teach PMs to solve problems independently, All of these ensure that your individual contributions and coaching efforts reinforce each other rather than work against each other. Over time, your team grows, and you free yourself to have a broader, more strategic impact.
...Read More
158 Views
Reid Butler
Cisco Director of Product ManagementDecember 19
This one is fairly easy, add value. We as Product Managers need to ensure that we are adding value for our organization by understanding the market (and our customers) and guiding the strategy to be successful in that market. It's easy to be a product expert, but we need to focus on being market and strategy experts. In my career, some key examples of adding value are: 1. Knowing My Market Better Than Anybody Else. When I am the expert on what our market needs, both short and long-term, I add significant value in defining and driving our strategy. My product can't be successful without this. When we are proven right in terms of our strategy definition and market validation, we win. 2. Build and Foster Relationships I work hard at establishing relationships around the organization where I am working. These enable me to be effective in cross-team collaborations and makes driving alignment across the organization easier. My relationships add value to me and my team. 3. Be an Expert When you are viewed as an expert and continually show your expertise in an area that is needed within the organization, it's easy to be seen as somebody who deserves that promotion. Show that your expertise drives direct value for your organization with clear successes.
...Read More
155 Views
Reid Butler
Cisco Director of Product ManagementDecember 19
Not sure I would call them hacks, but I have various things I do to manage both my workload, product execution and overall team management. 1. ToDo List Goes without saying. Be organized and find a system that works for you. Pen and paper? Go for it. Trello board? Do it. Adoption Notion? Fire away. For me, it's been about finding what system works for me and being relentless with it. My memory is generally solid, but our roles as PMs mean we shift a lot ,and keeping track of things is the only way to be successful. You don't want to be known as the PM that people have to remind about asks over and over again. 2. Manage Your Calendar with Precision I manage my calendar carefully. I block the time that I need for things like responding to interruptions and checking in with various projects each day/week. Unless it's critical, I won't move those slots and that allows me to stay organized and on top of things. 3. Kanban for the Win I have been using a Kanban-style prioritization process for over a decade. Allows me to easily see what's in flight, what I need to keep an eye on, and at any given time, what is top of the pile to focus on. Lots of great tools for this, like Trello. I try and keep it simple with a backlog of items, what's in flight, and then what's done. 4. Automate to Success So many of our daily tools have automation capabilities that we can leverage to help with the simple things. The more "little things" I can take off my plate the better off I am to focus on the value-added things in my workload. Don't fall into the trap of "it's just easier for me to do it this time". If there is a way to invest a small amount of time to automate repetitive tasks or items.....do it.
...Read More
153 Views
Reid Butler
Cisco Director of Product ManagementDecember 19
In my mind, it's not an either-or. By growing existing talent, you retain organizational knowledge and build a shared culture, while bringing in external hires inject fresh perspectives and sometimes specialized skills lacking within a PM team. When I am looking at my team structure and needs, I often consider the following: Things to Consider: 1. Internal Development Programs: Promote from within by offering training, mentorship, and rotational programs that broaden your team's exposure. This approach (in my experience) strengthens loyalty, develops institutional knowledge, and keeps your product strategy consistent. 2. Hire Externally: Often times PM teams get into stuck patterns and fresh perspectives are invaluable for a team's growth. When I need new capabilities, like a strong data analytics background, or experience in a specific market segment, hiring from outside will usually shorten the learning curve and bring proven experience to the team. This ultimately helps the broader team as their exposure to these new skills raises everybody's value and potential. 3. Do Both: We need to do both internal development and external talent acquisition to manage the best possible team. Keep growing your internal team by providing new opportunities and challenges, while selectively recruiting outside talent to fill knowledge gaps and bring in fresh eyes. This way, I keep our internal culture strong, ensure continuity / grow loyalty and still gain a fresh perspective when you need it.
...Read More
152 Views
Credentials & Highlights
Director of Product Management at Cisco
Product Management AMA Contributor
Top 10 Product Management Contributor
Knows About Product Development Process, Managing Mature Products, Product Management Career Path...more