Bugs that literally cost money
- The most obvious case of “obvious cost” is when the bug prevents you from spending money.
- Most of the price of a bug is indirect: lost consumer confidence, the opportunity cost of debugging, schedule impacts, etc.
- The critical path in a system is the sequence of events that ends with the customer giving you money.
- The code supporting the critical path needs to be more thoroughly verified than the rest of the supporting code because if it breaks, then you cannot make money.
- The path should be monitored more heavily in production and more often audited.
- Bugs outside the critical path can still be expensive, but it’s more likely to be expensive in an indirect way. Outside the critical path includes “code that delivers the stuff people want to pay for”, aka the actual product.
Some tactical advice on productivity
- Give a shit: You have to care about something that will drive you to get things done because if you don’t, apathy will occupy that void.
- Minimize uncertainty: Poorly defined goals can lead to poor productivity. If it’s unclear what you need to get done today, then there’s a reasonable chance you won’t do anything today.
- Commit to getting something done every day
- Do not overpromise to make up for poor productivity
- Never say, “I’ll finish it up tomorrow” or “I’ll make up for it by coming in early/staying late/working the weekend”: This is like racking up credit card bills assuming you can pay them off later, which is fine, until “later” arrives and you’ve only accumulated more debt.
- Have an objective productivity metric: If you judge your value solely on output, not subjective things like “being smart”, you will be more productive.
- Accept that “the grind” is part of the job: You can’t get irate or frustrated that the bulk of the day is typing in tedious code and dealing with bugs and other people.
Developing Positive Intelligence
- Positive Intelligence is the ability to control our mind to focus on our actions to shape our future instead of living in the past or worrying about an uncertain future.
- Our minds are made up of two distinct modes (i) Saboteur characteristics that are our enemies and (ii) Sage characteristics that are our friends.
- The relative strengths of Saboteurs and Sage’s characteristics determine our level of positive intelligence. In essence, increasing Positive Intelligence comes down to weakening our Saboteurs and strength of our Sage qualities.
- Weaken saboteurs by naming them and identifying their deep root cause, visualising them at their worst and identifying triggers and common saboteur patterns
- Strengthen your sage by developing empathy for yourself and others (showing appreciation, compassion, and forgiveness), exploring with curiosity and an open mind (observing without judging to sharpen the saw of curiosity and open-mindedness), choosing a path that best aligns with your deeper underlying values and mission, activating and taking decisive action without the distress / interference / distractions
What is Stripe’s Big Red Button?
- Stripe’s incident response tool, a service nicknamed the “Big Red Button” (or “BRB” for short), was first built around 2017 when the company was a few hundred people
- BRB was designed to create a dedicated Slack channel for each incident using a particular naming convention. BRB generated a name by randomly picking and combining two commonly used English words. (Eg: “#incident-friendly-llama”)
- This naming convention, combined with the idea of separate channels, came to be universally loved by Stripes
- BRB’s functionality expanded beyond kicking off incidents to include helping during incident response through post-incident follow-up.
- BRB addressed problems in the incident lifecycle: First, make it easy to report an incident and get the right people together and talk to each other, Second, add human-overridable tooling/automation to reduce the most tedious and error-prone parts, Finally, maximize what the org learns from each incident.
The New Approach to Personalization is all About Customer Behavior
- Personalization today is about contextualizing customer behaviour through more intelligent, more secure data.
- Beyond the clear benefits to ROI and maintaining customer loyalty, personalization gives brands a human edge over those still conducting business as usual.
- Businesses are adopting new ways to personalize the customer service experience with everything from being able to video chat with a customer to troubleshoot a product installation to text about a package delay instead of having to sit on the phone
- The future of personalization depends on the behavioural context that businesses can only get through first-party data
Others