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

What is our One Metric that Matters ? #149

Closed
nelsonic opened this issue Dec 22, 2016 · 16 comments
Closed

What is our One Metric that Matters ? #149

nelsonic opened this issue Dec 22, 2016 · 16 comments
Assignees
Labels
awaiting-review An issue or pull request that needs to be reviewed discuss Share your constructive thoughts on how to make progress with this issue enhancement New feature or enhancement of existing functionality help wanted If you can help make progress with this issue, please comment! priority-1 Highest priority issue. This is costing us money every minute that passes. question A question needs to be answered before progress can be made on this issue T2h Time Estimate 2 Hours

Comments

@nelsonic
Copy link
Member

nelsonic commented Dec 22, 2016

What is our "One Metric that Matters" http://leananalyticsbook.com/one-metric-that-matters/ ?
What is the one thing we want to measure @dwyl in order to do more of that thing...?

I really like the fact that GitHub let's you filter based on the "reactions" on an issue now:
github-filter-on-most-reactions
See: https://github.com/dwyl/hq/issues?q=is%3Aissue+is%3Aopen+sort%3Areactions-heart-desc

@nelsonic nelsonic added discuss Share your constructive thoughts on how to make progress with this issue enhancement New feature or enhancement of existing functionality help wanted If you can help make progress with this issue, please comment! priority-1 Highest priority issue. This is costing us money every minute that passes. labels Dec 22, 2016
@nelsonic nelsonic changed the title One Metric that Matters What is our One Metric that Matters ? Dec 22, 2016
@nelsonic nelsonic added the question A question needs to be answered before progress can be made on this issue label Dec 22, 2016
@Jbarget
Copy link
Member

Jbarget commented Dec 26, 2016

I dont have the answer to the question but I find this such an interesting discussion after being introduced to it by Tristan Harris at web summit.

Same talk here - https://www.youtube.com/watch?v=3OhMJh8IKbE

He has set up an initiative called Time Well Spent to combat the current trend in "successful" companies's focus being on the amount of Time Spent on their products by users. Makes so much sense.

@nelsonic
Copy link
Member Author

@Jbarget so stoked you got a chance to listen to Tristan @ WebSummit! 🎉
just that alone was worth your trip to Lisbon! ✈️
We were discussing this the other day and concluded we need to have the "Time Well Spent" design philosophy at the heart of what we are building see: dwyl/app#187 ❤️ ✅

Meanwhile the 🔍 for an OMTM for DWYL continues ...
Question: how can we formulate a Metric (something measurable) out of the "Time Well Spent" philosophy? 🤔

@ghost
Copy link

ghost commented Feb 3, 2017

I think one metric that might be interesting and/or useful would be Product Metabolism. Still looking into it and will update more later, but leaving this here in case anyone has any thoughts on it or other metrics.

@ghost ghost self-assigned this Feb 7, 2017
@ghost
Copy link

ghost commented Feb 14, 2017

Is there a way to track productivity as a metric? Maybe reflect on our productivity everyday and assign a quantitive amount to it as well as quantitative comments reflecting on the day?

@ghost ghost assigned nelsonic and unassigned ghost Feb 14, 2017
@nelsonic
Copy link
Member Author

I'd rather track happiness than productivity. but both are equally "subjective" ...
@iteles your thoughts on this would be welcome. 👍

@ghost
Copy link

ghost commented Feb 21, 2017

We can set up NPS scoring for happiness quite easily

@ghost ghost self-assigned this Feb 25, 2017
@ghost
Copy link

ghost commented Feb 27, 2017

@iteles your thoughts?

@ghost ghost added the blocker label Feb 27, 2017
@ghost ghost assigned iteles and unassigned ghost Feb 27, 2017
@nelsonic
Copy link
Member Author

HI @markwilliamfirth, I think we like the idea of the NPS ...
we just don't like the way most companies implement it ...
We don't want to make tracking happiness or "satisfaction" a "formal" thing people do because they have to ... it's like telling people to Tweet. if they don't want to do it then it will always feel like a "chore".

@ghost
Copy link

ghost commented Feb 27, 2017

@nelsonic how would you like to track it?

@iteles iteles removed their assignment Mar 1, 2017
@ghost
Copy link

ghost commented Mar 7, 2017

NPS tool I mentioned -> https://promoter.io

@nelsonic nelsonic assigned ghost May 5, 2017
@ghost
Copy link

ghost commented May 8, 2017

@nelsonic see comment: #149 (comment)

did you have further thoughts about how you wanted to implement NPS?

@ghost ghost assigned nelsonic and unassigned ghost May 8, 2017
@mantagen
Copy link
Member

mantagen commented May 23, 2017

@Jbarget @nelsonic
I recommend this podcast https://www.youtube.com/watch?v=jlPF9_1VIso
(Sam Harris and Tristan Harris)

@nelsonic
Copy link
Member Author

@mantagen listening to the podcast now. super-slow! had to 1.5 speed it...

@mantagen
Copy link
Member

mantagen commented May 23, 2017 via email

@iteles
Copy link
Member

iteles commented May 24, 2017

I've been going through this and discussing it with various people over the last few months, but this definitely needs to be codified.

The most important thing for people to realise is that 'One Metric that Matters' doesn't tie you into that metric forever more. As dwyl and our shared objectives evolve, we encourage a periodic review of these.

There are (and should be) OMTMs for each branch of the organisation and for individuals as well. There will be more detailed objectives, but it's crucial to have an OMTM so that there is a clear focus and expectation.

Individual Team Members

OMTM: Frequency and quantity of Shared learning.

Learning how to do something just so you can solve a particular problem on a project is fine, but if the knowledge goes no further than an individual, how useful is it and how quickly will you forget it?

We work together. We build each other up.

The people who share what they know (i.e. write/contribute to docs, blog posts, records screen casts and write books) are the ones who vastly exceed their peers. Sharing immediately demonstrates to your peers (and both current & future employers/team mates) that you are a "Lead Developer".

Remember that:

  • There's a high degree of certainty you will forget the details of how you "solved" something
    between writing the code and returning to it weeks later. Working your way through your code will waste your own time re-grokking it
  • 'Others' is not just people within your physical reach. We aim to be a remote-first organisation (meaning you can work from anywhere) and we already have a remote community of over 350+ people actively contributing to your knowledge
  • Your own learning is solidified by teaching
  • When someone takes an hour of their time to write up something that took them a day or a week to figure out and learn, you can now learn it in 30 minutes. Think about how much time you have saved! Pay it forward.

Shared Learning - How?

Contribute in the form of dwyl/learn-x enhancements and implementations of these learnings on dwyl modules/products.

Don't take our word for it, here's Mattias Petter Johansson from Spotify: https://youtu.be/RleN-6uMF04

image

All Projects & Product

OMTM: Number of Re-useable Components created (or used) in the project

If we are not writing re-useable code we are building everything "from scratch" each time.

This is worse for the client/customer/user because it takes longer to build (and is therefore more expensive) and longer to start getting actionable feedback from user testing.
It's worse for all future projects and team mates because it wastes future time of people and projects who have to constantly rewrite similar things.
It damages our chances of working with clients who are doing awesome things that have a real social impact because these are also often the clients with the least budget.

Number of re-useable components - How?

Track this and document at the end of each project.

Services Projects

OMTM: User Satisfaction with the end-result.

or, if we can't get access to this data:

Proxy OMTM: Product Owner Satisfaction in the form of a quote and rating

Both of these metrics will feed into the relevant case study for the project/client.

We then also want to integrate that feedback into our processes to make what we do better both for current and future clients.

User satisfaction/PO satisfaction - How?

In the short term, through surveys that are sent to POs at the end of a project.
We need to work with our clients to develop a way to help them measure end user satisfaction.

dwyl Products

OMTM: Number of people who have used the products to save time in their lives and feel more fulfilled.

Our goal as an organisation is to "Empower people to sustainably unlock their potential and pursue their passion."

Our products will be a conduit for this goal so we want to ensure they are making strides towards it.

Operations

OMTM: Ensuring all operating (financial and human) information is available in near realtime through automatisation of systems.

I see the key task towards this as automating as many systems as possible so the data flows and minimises repetitive manual input wherever possible. HOWEVER, we also need to do this in such a way that minimises tooling and keeps to our 'single source of truth' principle to ensure frictionless updating.

"Operations" is not directly responsible for bringing in revenue or creating the product, but is critical to saving everyone time and ensuring that all of the necessary information is readily available so that informed/good decisions can be made e.g. #321.

@markwilliamfirth @nelsonic NPS is a good metric we should track in the near future,
but in the short term, we have a simple way we can collect feedback: https://github.com/dwyl/feedback ❤️

@nelsonic nelsonic removed their assignment May 24, 2017
@iteles iteles removed the blocker label May 24, 2017
@nelsonic
Copy link
Member Author

nelsonic commented Jun 5, 2017

@iteles I saw you start to transfer these OMTMs to a markdown file ... but guessing you got lured away to a more urgent task. please assign PR when ready. thanks! 👍

@iteles iteles added the T2h Time Estimate 2 Hours label Jul 30, 2017
@iteles iteles added the awaiting-review An issue or pull request that needs to be reviewed label Aug 4, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
awaiting-review An issue or pull request that needs to be reviewed discuss Share your constructive thoughts on how to make progress with this issue enhancement New feature or enhancement of existing functionality help wanted If you can help make progress with this issue, please comment! priority-1 Highest priority issue. This is costing us money every minute that passes. question A question needs to be answered before progress can be made on this issue T2h Time Estimate 2 Hours
Projects
None yet
Development

No branches or pull requests

4 participants