Published on <a href="http://ift.tt/2v1pa5j">| Prototyping: From UX to Front End &mdash; Medium</a> C. Kyle Jacobsen <img alt="" src="http://ift.tt/2uH4Erc">
In March of 2017 I joined <a href="http://www.teem.com">Teem</a> to build a new product group and introduce and implement product management practices. Teem needed more predictability with their product development efforts and I committed to solving these problems. While interviewing with the executive team I proposed to understand, focus and improve six main areas:
<ol>
<li>Vision &amp; Strategy</li>
<li>Team &amp; Work Alignment</li>
<li>Communication</li>
<li>Users &amp; Personas</li>
<li>User Centered Design Practices</li>
<li>Professional Development</li>
</ol>
The following post describes why these topics are important for all product leaders, what we achieved and the problems we faced. I also include a week-by-week account of our first 90 days so you can see how we progressed.
<img alt="" src="http://ift.tt/2u8bb1b">
<h3>1. Vision &amp; Strategy</h3>
This is the first thing every product leader should understand when joining a new company. What is the vision of the company and how does this translate to strategy and the product? Without this, success is impossible because you need to know what direction to take the product (where to invest). Don’t be surprised if you find there isn’t much alignment here so don’t hesitate to jump in and create something.
Here is what I did to learn about vision and strategy at Teem:
<ol>
<li>I spent a week interviewing the executive team starting with the CEO. I asked each of them the same set of questions regarding vision and strategy and compared results.</li>
<li>I then interviewed the next level of management to compare results. No surprise really, but I found deviations from what I heard from the executive team. Just in case you are asking… yes, I did share this information with the executive team.</li>
<li>Next I analyzed where the development team had been investing resources. Please note that even if a team is aligned to the vision and strategy it doesn’t mean their work is aligned — more about this below.</li>
</ol>
Before any product leader can make an impact, they must understand if there is a vision / strategy, if people believe in it and if they are staying disciplined to achieve it. The first two are easy, the third is incredibly hard.
In the end, we formalized our product vision (which is really a product centric view of the company vision) in Week 12.
<img alt="" src="http://ift.tt/2uH6593">
<h3>2. Team &amp; Work Alignment</h3>
Wow, this is where all the emotions lie so trust me, there is no right way to do this but there are plenty of wrong ways. At this point I understood the vision and strategy but were we disciplined enough to achieving it? And were we aligned to make it happen?
Face it, as product leaders we are ultimately responsible to provide a product vision which aligns with the company vision (sometimes influencing the company vision) but more importantly, staying disciplined to achieve it. And before we can expect to change any aspect of team and work alignment we must realize the importance of building trust (just getting to know people). While building trust I asked a lot of questions like:
<ol>
<li>Are teams working on the right items?</li>
<li>Are the right people working on these items?</li>
<li>Do they have the right tools?</li>
<li>Do they have enough people?</li>
<li>Are they aligned in a productive manner?</li>
<li>Do they have the right skills?</li>
</ol>
At Teem we were doing a great job but needed to improve team and work alignment. So we made slight adjustments and here are some of our learnings:
On team alignment: I’m going to guess that most teams are either aligned by Users/Personas or by projects. Whatever the case, you need to make sure you have the right mixture of skills, personalities and people on each team. Consider working with your development lead(s) to pull this off and expect that it’s going to take a significant amount of time.
On work alignment: Consider this, identify the critical work (rely on the work you do for Vision and Strategy exercise) and share why it is critical for the company success. Ask the teams if they agree on this critical work and invite them in to discuss how they would solve these problems. I have found that asking for help and advice builds trust and makes the transition to critical work much easier.
Expect false starts. This part sucks but be ready to experience failure. People will say one thing and do another and this is probably because you haven’t done enough to gain their trust. I made this mistake. Don’t let this deter you. Get to know everyone better (especially their concerns) and work to get them aligned with the critical work items.
<img alt="" src="http://ift.tt/2u8gJbN">
<h3>3. Communication</h3>
This is probably the easiest of the six problems to solve and it’s something you can start solving immediately. I’ve learned that a successful product team is the hub of every business and thus communication from this team is critical. Confidence in a product team is a tricky thing and poor communication will erode any confidence others have in your team.
At Teem there was a lot of talk about “black holes” regarding product development work so this is where we started our efforts. We set out to make communication simple and predictable for all of our audiences.
<h4>Tools for communication:</h4>
Personal plea: can we please stop trying to retro-fit tools we use to track project progress for communication purposes? Face it, if you are using Jira or Trello it’s not going to succeed.
As product leaders we should be experts at delivering great user experiences so why not apply this skill internally? True, it may be easy for US but what about those who need the information? At Teem we use a method which is simple and accessible at all times which is centrally located in the building and accessible to all.
<img alt="" src="http://ift.tt/2uHb2yU">Version 1 of our product wall (obviously some content is confidential)
<h4>Cadence of communication:</h4>
This. Is. Simple. Find a cadence for each group and stick to it. Daily, Weekly, Monthly, Quarterly — whatever works. Make it predictable for everyone.
<img alt="" src="http://ift.tt/2u8pkLC">
<h3>4. Users/Personas</h3>
The age old debate over personas is something I don’t want to hash out — not here. But let’s just all agree, our teams should have a shared understanding of the buyers and users of our product. At Teem we know who our user is but as we learned more, we realized the need to start focusing on other users.
We began by speaking with every group in our organization: marketing, sales, developers, CSMs. We talked about buyers vs users and how the user role changes based on other variables, including market size.
Once we had a basic understanding, we started talking directly to users and validating our assumptions. When we were done we complied our findings in a simple, publicly displayed document.
<img alt="" src="http://ift.tt/2uHeolk">This is Chris, one of our users<img alt="" src="http://ift.tt/2u8l4fe">
<h3>5. User-Centered Design Practices</h3>
Teem needed this desperately.
Simply put, this is a process by which you connect those designing and building the things with those that use the things. If done correctly, your team will be able to create a solution which will solve the major issues of the market while not over-engineering solutions.
There are many different approaches to User-Centered Design practices and they can be summed up into three basic stages:
Discover or learn about the problem directly from the users, design a solution based on what you learn and test the design before you have the development team build something
To help introduce the concept of User-Centered Design practices we put up a poster explaining the process and I worked closely with the product team to implement practices supporting it.
<img alt="" src="http://ift.tt/2uHikm4">
Looking for a solid User-Centered Design practice? I recommend checking out Nate Walkingshaw’s <a href="http://ift.tt/2pk2ryz">Directed Discovery</a> process.
<img alt="" src="http://ift.tt/2uHllTh">
<h3>6. Professional Development</h3>
Ok, this is a no brainer. We should be in the business of turning product managers into product leaders. I’m not going to spend time pretending to be the best professional development leader but I’m certainly working towards that goal! Here are two areas I plan to focus on:
<ol>
<li>Is the product team getting better at practicing product management and UX?</li>
<li>Is the product team able to inspire and motivate others?</li>
</ol>
I believe if I can get these two basic questions right, I will help this product team grow into leaders and nothing satisfies me more than helping others grow.
So my first 90 days at Teem has passed and we are off to a great start. The next 90 days will bring about a deeper and more intense focus on each of these items and mentorship for the product team.
Check out the weekly breakdown of our first 90 days (below) and a huge shout out to those who made this happen: <a href="http://ift.tt/2u8gz4m">dal adamson</a>, <a href="http://ift.tt/2uHbSvs">Harley Jessop</a>, Deanna Walters and Morgan Williams. Also, thanks to those who have given us this opportunity: <a href="http://ift.tt/2u8r87y">Shaun Ritchie</a> and <a href="http://ift.tt/2uHb5e4">zach holmquist</a>.
<img alt="" src="http://ift.tt/2u8yVlE"><img src="http://ift.tt/2uH4GiO" width="1" height="1" alt="stat?event=post.clientViewed&amp;referrerSou">
<hr>
<a href="http://ift.tt/2u7Xcs9">Product Plan: My First 90 Days at Teem</a> was originally published in <a href="http://ift.tt/2cAqCpx">prototypr</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.

Product Plan: My First 90 Days at Teem

Top Stories