Wecomplish
Operationalization review
Basic concepts  

At any given time, there are expectations within a team that people

  • are unaware of
  • don't really understand
  • feel uncomfortable with
  • consider counter-intuitive
  • or perhaps even find unreasonable

As a result, these expectations are either not adhered to very well, or might require a lot of time, repetition, friction and followup to get done right.

One way to reduce effort and friction as a leader is to identify these poorly operationalized expectations and make them the subject of clarification, training or perhaps even reconsideration.

Ideally, we would focus our efforts on those expectations that, if made more easily digestible, would have the biggest impact to the confidence, morale and productivity of the team.

What if you could identify those expectations, at the click of a button? The operationalization reports aim to do just that by providing you with a ranking of how poorly understood and automated individual expectations are. 

This allows you to uncover new aspects of your business that you hadn't thought about, helps you spend your time more wisely, and focuses your efforts on where it will have the most impact.

Ranking system (impact score)

The ranking of expectations is based on an impact score calculated based on the familiarity data collected by the platform.

The impact score takes the following parameters into account:

  • The number of people expected to be familiar with the expectation
  • The current level of automation, broken down into
    • Familiarity: How familiar people are with the expectation
    • Clarity: To which degree people find the expectation unclear
    • Autonomy: To which degreee people have requested assistance with the expectation
    • Intuition: To which degree people are specifically focused on the expectation

The worse something is automated, and the more people are expected to be familiar with it, the higher the impact score.

You can see the impact score appearing in different places throughout the different operationalization reports. Here is an example:

Operationalization.png

Operationalization reports

The operationlization reports are available at different zoom levels in the organization.

Organizational report

The organizational report takes the most zoomed out perspective by ranking how well expectations have been operationalized within each team.

The awareness, familiarity and impact indicators reflect the average of the expectations within the team.

Skjermbilde 2022-11-20 kl. 06.07.04.png

Click a team card to zoom into the team operationalization report.

Team report

The team report exposes the individual the expectations within a team and ranks how well each individual expectation has been operationalized.

An expectation in this context is defined as a piece of insight which at least one role holder is expected to be familiar with.

The awareness and familiarity indicators reflect an average of the actuall awareness and familiarity as reported by the people expected to be familiar with it.

Here is what the top five items in a product team report might look like:

Skjermbilde 2022-11-20 kl. 05.45.54.png

Expectation report

Clicking on a specific expectation gives you a detailed view of how familiarity is distributed across the different familiarity levels. Here you can more easily discover if the low ranking is a result of a lack of people indicating their familiarity, or if the indicated familiarity levels are low.

Skjermbilde 2022-11-18 kl. 08.07.47.png

You can also request familiarity from the people who have not indicated it yet, by blicking the orange bell icon in relation to the "Unknown" familiarity label.

Person report

The person report exposes the featured expectations that a leader should focus on better operationalizing.

This report is accessible by navigating to the team focus of that individual, and selecting the Operationalization-tab.

Focus_on_team.png

The report displays all the teams that individual is responsible for, and the top 5 recommendations as identified by the impact score, or overridden recommendations.

Overriding recommendations

There is only so much the system knows about your organization. As a result, you should not blindly accept the top ranking expectations as the ones to focus on.

Some expectations might take precendent due to circumstances or their expected impact on overall work.

You can combine system insight with your own personal insight by overriding recommendations. This is done by clicking either the "Pin recommendation" or "Reject recommendation" buttons, moving the recommendation to the top and bottom of the list respectively.

Generate/update report data

As the team and its amount of expectation grows, calculating the impact of each expectation can get time consuming.

To preserve the performance and user experience of the platform, report data is generated on demand, and cached for future page requests.

Generating, updating and removing the report data cache for a team is done on by manually by clicking the "Generate report"/"Refresh report" buttons on the organizational or team reports.

Recommendation overrides are lost when report data is cleared or regenerated. However, any user attempting to clear or regenerate report data will be made aware of and prompted to confirm deletion if any overrides exist.

Undersider
Vedlegg

Relevant dokumentasjon

Laster...

Timeføring

Laster...

Bekreftelser

Laster...

Kjennskap

Laster...

Bokmerker

Laster...

Bakgrunnsjobber

Laster...