Product & Engineering's Ability: Decomposition & Sequencing


Description

Being able to understand the full scope of a project and working with the team to breakdown and sequence work that delivers value to our customers in iterations - aka a deliverable piece of functionality that works end to end in some meaningful way. It allows us to start collecting feedback from users.

An “iteration” is a shorthand for “a work item that delivers a valuable change in system behavior such that you’ll probably have to touch multiple architectural layers to implement the change.”

When you call the iteration “done,” the system is observably more valuable to a user.

Milestone 1

(adds 1 mile to your journey)

I have observed this person showing a consistent, comfortable, continuous, and clear positive impact to a squad when wielding this ability, and therefore I would put them in situations where they can employ this ability with only a small amount of guidance


  • Working with the team for the successful decomposition of ideas into shippable units of work to deliver customer value, validate P&E assumptions or both.
  • Though you may not be leading the effort, you consistently make valuable contributions throughout the journey

Milestone 2

(adds 3 miles to your journey)

I have observed this person showing a consistent, comfortable, continuous, and clear positive impact to a squad when wielding this ability, and therefore I would put them in situations where they can employ this ability, with no assistance as well as being a trusted active or passive mentor to others


  • Leads the squad in efforts of successful decomposition of ideas into shippable units of work to deliver customer value, validate P&E assumptions, or both
  • Develops right-size size iterations of work that fit into the checkpoint and quarterly goals
  • Thinks through the stack in a way that promotes flexible story creation (e.g. model/database, API, routes, react components, UI).
  • Your squad consistently gets iterations of work into customers hands for testing as early as possible in the lifespan of a project

Milestone 3

(adds 6 miles to your journey)

I have observed this person showing a consistent, comfortable, continuous, and clear positive impact to multiple squads when wielding this ability, and therefore I would put them in situations where they can employ this ability as well as being considered an expert within this discipline


  • Helps in establishing and bettering the way our decomposes and sequences delivery work
  • Identifies gaps in our existing process across squads and works to implement solutions to any gaps we have
  • Sequences for continuous progress by teams with shifting skills and availability (as teams have members with different skill sets, strengths, weaknesses, and availability)
  • Degrades gracefully: delivery is incremental enough that missing a target scope for a checkpoint or quarter still delivers usable scope; delivery isn't a binary proposition (which means eating into the subsequent quarter to save an initiative).

Milestone 4

(adds 12 miles to your journey)

I have observed this person showing a consistent, comfortable, continuous, and clear positive impact to a squad when wielding this ability, and therefore I would put them in situations where they can not only employ this ability but where they set the tone for this at the company level


  • Defines and promotes a long-term vision for how we decompose and sequence work across our department coordinates across the team to ensure projects are in service of it.
  • Goes externally to look for ways/best practices of decomposition/sequencing of work and brings those learnings back to Lessonly to consider

Milestone 5

(adds 20 miles to your journey)

I have observed this person showing a consistent, comfortable, continuous, and clear positive impact to not just internal teams but the community/industry in general when wielding this ability, and they are recognized by the community/industry as an expert


  • Implements new Forecasting and Estimation techniques and frameworks to meet the needs of the wider community.
  • Speaks at conferences/meet-ups about our Lessonly forecasting and estimation processes
  • Publishes articles/posts about best practices of estimating/forecasting as a team

Configuration Health

  • ✅ Associated with 6 roles
  • ✅ Has been referenced in 1 piece of public recognition
  • ℹ️ No one has achieved a milestone on this ability
  • ⛔️ Last updated: about 5 years ago
  • ℹ️ Never conversed about

Role & Position Requirements

Examples / Observations

  Observation created almost 6 years ago

This thread speaks to it: https://lessonly.slack.com/archives/CPHPVJSTH/p1574698910011200

This is a great discussion and approach to taking on what could be a larger project in Linked Elements. The team was able to work together to identify and slice up the work in order to get value into the hands of customer faster. Alec said it in his summary here:

We are going to structure the epics so at the end of each element the element is fully implemented. This means that at the end of epic two the paragraph element will have all of the linked element functionality. Then epic three will be the photo element fully implemented.

  • This will mirror how the platform team rolled out a role management, a fully functional piece of a larger whole. This means we can learn more about the entire linked element process earlier.
  • It gets to value quickly. We have been hearing for years from clients about the linked element functionality. With this plan, we will allow admins to do this whole process faster!
  • It will make the delivery manager role more smooth. Because of this plan, each epic will look similar technically speaking. The first element will take the longest because we have to implement all of Linked elements but after we will be able to determine with reasonable accuracy how long each element takes to build start to finish.

As a result...

  • This enables the squad in efforts of successful decomposition of ideas into shippable units of work to deliver customer value, validate P&E assumptions, or both
  • Developing right-size slices of work that fit into the checkpoint and quarterly goals
  • Thinking through the stack in a way that promotes flexible story creation (e.g. model/database, API, routes, react components, UI).
  • Your squad consistently gets slices of work into customers hands for testing as early as possible in the lifespan of a project

Conversations about Decomposition & Sequencing

This section is for Lessonly folks only. Sign your team up to find your Gruuv!

Embed code

<iframe src="http://ourgruuv.com/our/powers/44?embed=true&name=decomposition_sequencing&organization=lessonly"></iframe>