mirror of
https://github.com/fleetdm/fleet
synced 2026-05-23 17:08:53 +00:00
values 2.0 (#3666)
overhaul, smoh-ver-haul bring in values from https://gist.github.com/mikermcneil/f776a8e2010a2deb5274c2bcedc96cfe
This commit is contained in:
Mike McNeil
GitHub
parent
3c9eaad09c
commit
51cd0ff148
1 changed files with 119 additions and 36 deletions
|
|
@ -19,47 +19,130 @@ When Kolide's attention shifted away from Fleet and towards their separate, user
|
|||
### 2020: Fleet was incorporated
|
||||
Zach partnered with our CEO, Mike McNeil, to found a new, independent company: Fleet Device Management Inc. In November 2020, we [announced](https://medium.com/fleetdm/a-new-fleet-d4096c7de978) the transition and kicked off the logistics of moving the GitHub repository.
|
||||
|
||||
## Values
|
||||
|
||||
_Fleet's company values are a work in progress, with [an upcoming overhaul](https://gist.github.com/mikermcneil/f776a8e2010a2deb5274c2bcedc96cfe)._
|
||||
|
||||
### Quickly with craft
|
||||
|
||||
#### Iterate by taking baby steps.
|
||||
|
||||
We try to always make the minimum viable change. Small changes provide faster feedback, and help us to stay focused on quality.
|
||||
|
||||
#### Help each other get all the way done.
|
||||
|
||||
We collaborate and help our teammates to see tasks through to completion.
|
||||
|
||||
#### Focus on fewer tasks at one time.
|
||||
|
||||
By focusing on fewer tasks at once, we are able to get more done, and to a higher standard, while feeling more positive about our work in the process.
|
||||
|
||||
#### Role play as a user.
|
||||
|
||||
When making changes, we put ourselves in the mindset of the end user. We keep in mind how someone might use the product for the first time, or how an existing user might react to a new change.
|
||||
|
||||
#### Reread anything you write for users.
|
||||
|
||||
We check everything that a user might read for clarity, spelling errors, and to make sure that it provides value.
|
||||
|
||||
#### Review and merge PRs daily.
|
||||
|
||||
We value constant iteration and feedback. Reviewing and merging PRs daily keeps our open source community thriving.
|
||||
|
||||
### Patch with care
|
||||
|
||||
Patches improve security, usability, and performance. We may cut a patch release if there is a security concern, previously stable features are unusable, or if a new feature advertised in the current release is unusable.
|
||||
|
||||
|
||||
## Culture
|
||||
|
||||
### All remote
|
||||
Fleet Device Management Inc. is an all-remote company, with team members spread across 4 continents and 7 time zones. The wider team of contributors from [all over the world](https://github.com/fleetdm/fleet/graphs/contributors) submit patches, bug reports, troubleshooting tips, improvements, and real-world insights to Fleet's open source code base, documentation, website, and company handbook.
|
||||
|
||||
### Openness
|
||||
The majority of the code, documentation, and content we create at Fleet is public and source-available, and we strive to be broadly open and transparent in the way we run the business; as much as confidentiality agreements (and time) allow. We perform better with an audience, and our audience performs better with us.
|
||||
|
||||
## Values
|
||||
|
||||
### 允 Openness
|
||||
|
||||
The majority of the code, documentation, and content we create at Fleet is public and source-available, and we strive to be broadly open and transparent in the way we run the business; as much as confidentiality agreements (and time) allow. We perform better with an audience, and our audience performs better with us.
|
||||
|
||||
- be transparent
|
||||
- candor (faster, better decisions)
|
||||
- speak up (don't be afraid to ask questions, be direct, and interrupt)
|
||||
- [open source is forever](https://twitter.com/mikermcneil/status/1476799587423772674)
|
||||
- "public by default"
|
||||
- declassify with care
|
||||
- prioritize accessible terminology and simple explanations to provide value to the largest possible audience of users
|
||||
- anyone can contribute
|
||||
- open source stewardship: the majority of the features Fleet releases will be free, [etc](https://fleetdm.com/pricing)
|
||||
- hospitality
|
||||
- "be a helper" -mr rogers
|
||||
- think and say [positive things](https://www.theatlantic.com/family/archive/2018/06/mr-rogers-neighborhood-talking-to-kids/562352/)
|
||||
- be customer-first
|
||||
- but apply customer service principles to all users, even if they never buy Fleet
|
||||
- be outsider-friendly (inclusive)
|
||||
- approachable
|
||||
- talking with users and contributors is time well spent
|
||||
- embrace the excitement of others (it's contagious)
|
||||
- make small talk at the beginning of meetings
|
||||
- be our guest
|
||||
- believe in everyone
|
||||
- legendary hospitality
|
||||
|
||||
### 情け Empathy
|
||||
- consider your counterpart
|
||||
- assume positive intent
|
||||
- role play as a user, contributor, or colleague
|
||||
- be punctual
|
||||
- end meetings on time
|
||||
- bugs cause frustrating experiences and alienate users
|
||||
- confusing error messages make people feel helpless, and can fill them with despair
|
||||
- error messages deserve to be good (it's worth it to spend time on them)
|
||||
- UI help text and labels deserve to be good (it's worth it to spend time on them)
|
||||
- contributor experience (but quality and commitments first)
|
||||
- developers are users too (REST API, fleetctl, docs)
|
||||
- design by consumer (closeness to the work)
|
||||
- use fewer words (lots of text == lots of work)
|
||||
- prioritize simplicity: people crave mental space (in design, in collaboration)
|
||||
- cognitive unload (via clarity, fewer and smaller words, fewer acronyms and idioms that might not translate)
|
||||
- but think fast, because i.e. "I would have written a shorter letter, but I did not have the time." -Blaise Pascal
|
||||
- legendary digital/human experience
|
||||
|
||||
### 任 Ownership
|
||||
- take responsibility
|
||||
- follow through on commitments (actions match your words)
|
||||
- prioritize honesty and kindness
|
||||
- think like an owner
|
||||
- be efficient
|
||||
- be valuable (consider business impact)
|
||||
- work on things that matter
|
||||
- fast forward 12 months, consider total cost of ownership (the eternity of maintenance)
|
||||
- understand why
|
||||
- agree, or disagree and commit anyway
|
||||
- make time for self-care (to help you bring your best self when communicating with others, making decisions, etc)
|
||||
- consider taking a break and going for a walk
|
||||
- think about how to best organize your day/work hours to fit your life while maximizing value for the company
|
||||
- help unblock users, customers, and other contributors (including colleagues)
|
||||
- help team members and contributors get all the way done, delivered all the way to completion
|
||||
- we win or lose together (it's worth it to help team members and contributors)
|
||||
- less is more
|
||||
- "boring solutions"
|
||||
- prefer short calls to long, asynchronous back and forth discussions in Slack
|
||||
- avoid bikeshedding
|
||||
- bite off what you can chew
|
||||
- finish what you start, or at least throw it away loudly in case someone wants it
|
||||
- focus on fewer tasks at one time
|
||||
- legendary execution
|
||||
-
|
||||
|
||||
### 出来 Think, fast
|
||||
- think for yourself (only you can)
|
||||
- from first principles
|
||||
- use reason
|
||||
- believe in your brain's capacity to evaluate a solution or idea, regardless of how popular it is
|
||||
- take your own ideas seriously (great ideas come from everyone, write them out and see if they have merit)
|
||||
- take your own results seriously
|
||||
- on a hero's journey
|
||||
- you are capable of epic results
|
||||
- even boring tasks are more motivating, fun, and effective when you care
|
||||
- motivate yourself intrinsically with self-talk
|
||||
- understand "why?"
|
||||
- take pride in your results
|
||||
- reread anything you write for users
|
||||
- you don't need permission to be thoughtful
|
||||
- every real-world edge case deserves handling (be thorough)
|
||||
- BUT balance thoughtfulness and planning, with moving quickly:
|
||||
- "everything is in draft"
|
||||
- pick low-hanging fruit (deliver value quickly where you can)
|
||||
- avoid gold-plating
|
||||
- aim to deliver daily
|
||||
- move quicker than 90% of the humans you know
|
||||
- iterate by taking baby steps
|
||||
- legendary results
|
||||
|
||||
|
||||
### 真 Objectivity
|
||||
- be wrong
|
||||
- show your work
|
||||
- be realistic (practical about your limits and what's possible with the time and resources we have)
|
||||
- speak computer to computers (assume it's your fault)
|
||||
- question yourself (why do I think this?)
|
||||
- use the scientific method when something isn't working
|
||||
- listen intently, and genuinely try to understand
|
||||
- facts, over commentary
|
||||
- ask great questions & take the time to truly listen
|
||||
- "strong opinions, loosely held"
|
||||
- prioritize truth (reality)
|
||||
- beware sunk cost fallacy (avoid getting attached to something just because you invested time working on it, or came up with it)
|
||||
- be curious
|
||||
- legendary rigour
|
||||
|
||||
|
||||
|
||||
<meta name="maintainedBy" value="mikermcneil">
|
||||
|
|
|
|||
Loading…
Reference in a new issue