Description
You identify needs on the team and take steady steps to meet them. You rethink the status quo, and when processes or practices could be better, you bring people together to improve them.
Milestone 1
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
When you notice ways the team or product could be better, you say something.
For example:
- Reflects often in #product-team-huddles about improvement opportunities on the team.
- Raises questions that are on others’ minds, such as "Why do we do this?" when that isn’t clear.
- If it's a bug, report it. If it's an enhancement, you talk to someone about it (PM, Principal Prod Designer, etc)
Milestone 2
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
When you notice ways the team or product could be better, you try to do something about it.
For example:
- Joins Do Better Work Committees to bring others together to make a positive change.
- For issues unable to fix on one’s own, identifies who should be responsible and sees that they address it.
- Identifies practices that have outlived their usefulness and phases them out responsibly.
Milestone 3
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
When you notice ways the team or product could be better, you make it better in impactful, measurable ways.
For example:
- On Do Better Work Committees, sets milestones and metrics tracking positive impact to the team and delivers on them.
- Takes responsibility for neglected systems and processes (e.g. anything from "Ebert is broken." to "The recycling is piling up.") by creating structures to see they've taken care of on an ongoing basis (e.g. maybe an #ebert-caretakers Slack channel or a recycling rotation.)
Milestone 4
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
Rethinks fundamental aspects of how our team or product work, and leads steady, measurable progress to their realization.
For example:
- Leads the transition from project-based waterfall teams to continuously•delivering agile squads.
- Identifies the need for a brand new role on the team and owns the process of hiring to fill it.
Milestone 5
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
Effects change that has a substantial positive impact on the whole company.
For example:
- Rethinks the department’s responsibilities to better achieve our company vision.
- Identifies the need for a new product strategy and coordinates implementing it across all affected departments.
- Changes complex organizational processes for the better.
Configuration Health
- ✅ Associated with 9 roles
- ✅ Has been referenced in 14 pieces of public recognition
- ℹ️ No one has achieved a milestone on this ability
- ⛔️ Last updated: almost 6 years ago
- ℹ️ Never conversed about
Role & Position Requirements
- Back End Engineersmust be milestone 1+
- Company Level Dbw Initiative Membersare recommended to be milestone 1+
- Design System Contributorsmust be milestone 2+
- Front End Architectsmust be milestone 2+
- Front End Engineersmust be milestone 1+
- Onboarding Buddiesmust be milestone 1+
- P&E Dbw Group Membersmust be milestone 1+
- Product Engagement Analystsare recommended to be milestone 2+
- Solution Designer (Ux Design)smust be milestone 1+
Examples / Observations
Observation created over 4 years agoShout out to Ellie on her last day for just being a great teammate. I've really appreciated her willingness to be flexible as the Practice squad has needed to shift priorities and direction a lot in her time with us. She's always been available and ready to help when I've been stuck with front-end things (and those times have been plentiful lately). You've been such a reliable part of the team since you've been here and we will definitely miss you on Practice!
Observation created almost 5 years agoFeaturing:Stephen G.Engineering CommunicationInitiativeStakeholder / Feedback ManagementDevOps Enablement LeadUnexpected, concise, clear, communicated with both summaries and details, and action-oriented. As it pertains to emails about technical topics, it doesn't get much better than this.
I now feel that much more confident that Stephen isn't just thinking about doing the tasks he is assigned... he is thinking about the overall picture and health of Lessonly as we navigate this journey we are on.
Love it!!
Email #1:
HI everybody,
As you may or may not be aware there was a massive hack on solarwinds which provides infrastructure software to many companies. ( https://www.solarwinds.com/securityadvisory ).
I want to present to this group the (preliminary) findings as I investigated our exposure because industry-wide implications and more customers are going to be asking about this. It is going to be beneficial to have some sort of statement to respond with.
If you would like me to work with somebody on what that statement should be please let me know. And if you have any guidance on verbage before we craft such a statement I would appreciate it.
Executive Summary
We use a small unaffected Solarwinds product in non production environments. A couple of our vendors had similar exposure. Our biggest risk is Twilio which actually used an affected product, but they believe they were not impacted by the breach.
Our Direct Exposure
We do not use their software directly in our data centers.
PaperTrail
We use a product called PaperTrail in non-production environments for logging. No sensitive information should be sent there. This product
Vendors
Vendors known to have some exposure to SolarWinds Products
Twilio (Sendgrid, Twilio, Segment)
The company Twilio owns 3 services that we use. Twilio did use the affected software "in a limited fashion." They have been working with SolarWinds and believe they were ultimately unaffected by the breach
Twilio is our biggest risk, but at this point I believe it to be mitigated.
Harness
Harness used an unaffected SolarWinds product (Pingdom). Ultimately I see no risk here, but they did share this for transparency.
CloudBees (Codeship)
CloudBees owns the codeship product that we use. They, like Harness, used some unaffected SolarWinds products
Librato (scoped to our CodeShip product)
PaperTrail (scoped to our CodeShip product)
PingDom (basic external monitoring used by Ops)
Observation created almost 5 years agoFor starters, I was impressed by the quick turnaround to remove courses from Copy Company. It came up earlier in the day, and then oh what's this, a PR is already ready to be reviewed? Happy to pick it up, especially since it's something that benefits Learn next quarter. 🙌
But the quickly-moving PR is especially impressive because the notes were dense with Classic Steve Thoughtfulness.
"Why do we care about removing courses from Copy Company?"
"How can we be sure that we're safe to do so?"
"What even IS Copy Company?"These are questions that each have multiple answers in Steve's PR notes. Even though I've worked with Copy Company a few times, I still felt like I was learning something. I felt empowered to give a review and move this along in the process, because I knew that Steve had explored the potential risks around giving this code the axe.
Here is the PR in question! https://github.com/lessonly/lessonly/pull/9093#pullrequestreview-523805875 As someone who always favors more over less when it comes to context and supplemental information, I appreciated these notes a lot!!! 🤩
Observation created about 5 years agoA few of the many things I appreciate about Brittany, all demonstrated in this PR:
She goes out of her way to make things better for the rest of us. The whole purpose of this PR is to 1) enable developers who don't normally work with Algolia to understand how to do so more easily, and 2) to remove hard-coded data from our code and make a whole process more dynamic and much better. AR3 says to leave things better than you found it, and I see Brittany doing that here (not for the first time, and surely not for the last!).
She makes a point to communicate thoroughly and clearly. There are a lot of notes on this PR! I know many of us enjoyed her lightning talk last transition week, but beyond being funny and well done, that chat and this PR demonstrate how much time she puts into carefully choosing her words and crafting her sentences so that the rest of us know exactly what we are reading. For you non-devs, writing PR notes is often viewed as a chore that many of us do as minimally as possible, but Brittany puts effort into it for the benefit of the rest of us.
She's entertaining in the midst of already being awesome in all the other ways. I know this is a gift more than a skill, but she does it so well. I actually get a hint of excitement when I pick up one of her PRs 😄
Observation created over 5 years agoI am beyond impressed by this initiative and overall craftspersonship
:sob: :point_left::skin-tone-5: tears of pure joy.
More specific:
I think the main thing I’m going to do is create a Practice Tech Debt epic (I want to figure out what some of our biggest pieces of debt are)
- It is incredibly easy to just keep trucking along and idly hope someone else does something you know to be right. It is incredibly difficult to stop, and say "this... we... can be better"....
break them up into the tiniest and most informed stories I possibly can. That way, when we have awkward amounts of time, or we just want a semi-mindless task to do as a break, we can grab one of those stories and execute it. This will hopefully help us tackle things better than stories to remove an entire feature.
- ... It is damn near impossible to then actually devise a way to do that which actually has a shot of being adopted.
if y’all have any ideas for things I could add, please comment them here. I’m especially wondering if those of you who have been working in the front end for ziggeo know of any components we can refactor or :knife:
- One of the rarest things is to be able to do all of that and bring others along with you.
The last three ingredients of the "Sense and Respond" + "Goal Setting" + "Systems Management" trio of multiplicative leadership (AR3 trademark pending :fblaugh:) are:
- Establishing an observable and actionable feedback loop
- Inspiring others to care about that feedback loop in such a way that it changes their behavior
- Learn from the loops taken, and make the thing you are trying to accomplish better after every iteration
I want to be crystal clear... I put these here, not to diminish the absolute joy I have about the slack post in question... but, hopefully, as inspiration to (and maybe a bit of a guide to) continue going :slightlysmilingface:
Regardless of what happens, the sheer awareness, initiative, and thoughtfulness is worthy of significant recognition :pray::skin-tone-5:
Conversations about Initiative
This section is for Lessonly folks only. Sign your team up to find your Gruuv!