I was recently discussing with a colleague the two distinct parts of my job: Engineering Team Manager and Software Product Director. In one half I am responsible for the cohesion of the team, supporting and growing team members, and employee exits. In the other half I am responsible for the cohesion of the product vision, support and growing the product features, and retaining clients.
I see a lot of overlap in the work I do in each half but often these two sets of responsibilities don’t come together in a single position. My colleague suggested that I outline a day in the life in this kind of position and see if it resonates with anyone else. And so this is my attempt to do just that.
8:00 Get situated
Review any emails or Slack messages from yesterday that need responded to. Make a list of to dos or promises in progress. Prep anything needed for meetings for the day
8:30 One-on-one
Talk with a team member about their current work assignment and where they are struggling with some technical skills. We set up a mentorship plan with one of the more senior members of the team. Then we transition to talking about their long term growth plans and check to make sure the current work assignment matches with their development goals.
9:00 Standups
Three teams, three standups, three completely different conversations and engagement styles. One team jokes about upcoming lunch plans and then quickly walks through the board top to bottom. One team stops at the first story and get going on a technical debate on approach before I ask if we can take that to our planning. One team goes member by member and seems a little disengaged. I make a note to circle back on the last time to see what team building we can do.
10:00 Design Meeting in Planning
After setting it aside in standup, the team wants to immediately get into a debate on approach in planning. We pull out the digital white board and I start drawing out what I am hearing them say as the debate continues. Soon everyone on the team is drawing out ideas as well and we are settling into a rhythm of collaborative problem solving. I quickly review the market goals of the product we are developing and remind the team where it fits into our overall architectural goals as the discussion goes off into a debate that is not necessary for the immediate problem. Once we all agree on the approach, we turn it into stories and get into planning for the week.
11:30 Lunch
12:00 Re-situate
Look through any emails and Slack messages that came during planning to make sure that nothing needs my immediate attention. Add things that can wait to my to do list, respond to things that can be dealt with immediately. Fortunately, not very much needs urgent attention so I look down my list and calendar to find the next most valuable work.
12:30 Roadmap Presentation Prep
Given the relative quiet of the day, I find some focus time to work on the roadmap presentation I am recording later this week for clients. Put together screenshots of recently released features and outline how I want to describe what is coming next in our products. Review the project plans on the current products against our actual sprint work to ensure I will not be making promises we can’t deliver on. Send an update to the Exec sponsor of one of the products to tell them we are releasing a feature soon they will be especially interested in.
2:00 Open Office Hours
Open my Slack channel for Ask an Engineer and wait for a client facing support staff to ask a question. I quickly end up explaining how the object relationships of some data are impacted the way the information is showing up on the page to one person. Then I get into a discussion of our roll out of a new feature to clients with another.
3:00 Respond to Client Issue
Out of Open Office Hours I have one take away to work through a client issue with the development team. A client has expressed concern with how one of the products is working. I work through the client concern with the team and draft a message back to the client explaining our solution to the concern.
3:30 Huddle on a Proposal
The Sales Director has a prospect with a unique use case for one of our products we wants to talk through with me. We review the prospects needs and the different ways we can use our product to solve it. We come up with a good solution that won’t require any custom development and should work for their budget. I message a member of the client support team I worked with during open office hours to see if we can use one of their clients as an example.
4:00 Review Market Research
With the goal of finishing a draft of my client roadmap presentation, I review the market research for one of the products I want to talk about to ensure the development plan we have in place is supported by our understanding of the market needs. I listen through a problem interview I had recently with a client on that topic and pull out some phases they use for the notes on my slides.
5:00 Close out the Day
I take a moment after saving my presentation to look through my promises in progress list and check off what got done. Then make a note for the next day to think about ways to increase engagement in standups for team three. Close my book, and leave.