Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

added small team responsibilities, defined the role of the team lead and cleared up how PMs work with engineers #4261

Merged
merged 10 commits into from
Sep 25, 2022

Conversation

lharries
Copy link
Contributor

@lharries lharries commented Sep 22, 2022

We've are shifting from teams being based around geographies to small teams owning areas of the app. This has resulted in some confusion around:

  1. what are the responsibilities of these teams
  2. what actions should they be doing
  3. which parts do the team leads need to do
  4. how do the product managers fit into this

This is a first draft of an attempt to answer these questions.

@lharries
Copy link
Contributor Author

@annikaschmid @timgl @benjackwhite @EDsCODE @mariusandra @jamesefhawkins @yakkomajuri this is based on conversations we've had. Would be great to get your input on this

Co-authored-by: Ben White <ben@benjackwhite.co.uk>
Copy link
Member

@pauldambra pauldambra left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Few questions and comments but overall better that we have this 💪

@lharries lharries changed the title added app small team responsibilities added product small team responsibilities Sep 22, 2022
@lharries lharries changed the title added product small team responsibilities added small team responsibilities, defined the role of the team lead and cleared up how PMs work with engineers Sep 23, 2022
@lharries
Copy link
Contributor Author

lharries commented Sep 23, 2022

@jamesefhawkins, @timgl and co - I've addressed the above comments.

Let me know what you think and approve it if you think we are ready to merge - or let me know if there are other parts you think we should address.

Copy link
Collaborator

@timgl timgl left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry, hadn't had time to look at this yet. All the discussions above were great and have led to the right outcome here, so I'm happy to merge!

@jamesefhawkins
Copy link
Contributor

jamesefhawkins commented Sep 25, 2022

I'm going to merge. Thank you everyone for contributing.

@lharries I made a couple of tweaks (see final commit) , just to simplify:

  • each small team doesn't have to have a mission/vision and metrics (given just OKRs are new already - and there is a lot of overlap here)
  • I have deliberately left in they should have a customer. I think this is something we are not doing well at the moment. We have an ideal customer profile, but it's the same for everyone and could be much more precise by small team. Might be something you want to think about.
  • I also made you responsible that we don't have anything not covered properly in the product (rather than Tim). Not sure this is a big deal and I may be wrong with this change!

I'm merging as this is better than what we had, feel free to open future PRs to address the above as you see fit

@jamesefhawkins jamesefhawkins enabled auto-merge (squash) September 25, 2022 21:25
@jamesefhawkins jamesefhawkins merged commit 30189a0 into master Sep 25, 2022
@jamesefhawkins jamesefhawkins deleted the luke/team-lead branch September 25, 2022 21:50
In certain cases, but not everywhere. This will clarify where people will work. In fact, it'll make sure we keep the scrappy fun side of working here as we get bigger. A team doesn't _have_ to be six people.
In general, no - it's surprisingly great how much just 2-6 people can get done.

If more mature product areas cannot cope with the workload, smallt eams will clarify where we need to hire too. In fact, it'll make sure we keep the scrappy fun side of working here as we get bigger. A team doesn't _have_ to be six people.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

typo! smallt eams

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

10 participants