1/ "We expect that anything can happen and we are never prepared for anything"

This sentence resonated a lot with me

Regardless of the risk management, regardless of being adaptative, regardless of how prepared do you think you're, World keeps surprising you
2/ As a manager, your job is to make the teams, product, and business more resilient and adaptative to survive in several situations.

Yet, I never felt that we reached a level where we can say

"We're safe!"

It's not viable.
3/ You manage the areas that are more probable to happen and the impact is higher. Then, you just accept those situations that are outside that scope, to be handled as you can.
4/ What I found is that a resilient team with a good adaptative mindset and skills to perform better than aiming to prevent risks. As always, it's a trade-off.
5/ When hiring, I look for Adaptability Quotient and Emotional Quotient. They tend to perform better on high stake situations and fast-changing ecosystems as it's software today.
6/ Adaptative socio-technical systems can perform better in facing adverse situations.

DevOps and Continuous Improvement Mindsets play well here.
7/ I see an analogy to how we are creating software today.

Should we put more effort into ensuring we don't add a bug to production using tests or into the tooling to notice that something went bad to production and recover fast?
8/ At the end, we should be guided by

"What's cheaper?"

and the answer is a trade-off on multiple dimensions.
9/ The best is to do this exercise with the team and stakeholders so we all commit when some risk situation happen and play well together

• • •

Missing some Tweet in this thread? You can try to force a refresh
 

Keep Current with Aleix Morgadas 💉💉

Aleix Morgadas 💉💉 Profile picture

Stay in touch and get notified when new unrolls are available from this author!

Read all threads

This Thread may be Removed Anytime!

PDF

Twitter may remove this content at anytime! Save it as PDF for later use!

Try unrolling a thread yourself!

how to unroll video
  1. Follow @ThreadReaderApp to mention us!

  2. From a Twitter thread mention us with a keyword "unroll"
@threadreaderapp unroll

Practice here first or read more on our help page!

More from @aleixmorgadas

Mar 2
1/ I cannot stress enough the importance of junior people in the organization

I'm amazed by how much you learn when working with them. They really show where the organization/team can do better. It can be uncomfortable because they are sharing your weaknesses
2/ Don't think that they should know better to do the job, but why do we create a place where juniors cannot contribute or they have a hard time providing value? What can we do better to help them perform and learn faster?
3/ Juniors help Seniors find their weaknesses, more than seniors helping seniors. Since they show the areas to improve so easily!

- Why take that long to understand this code?
- Why is so hard to do a unit test?
- Why do they get lost in the code structure?
Read 5 tweets
Mar 1
1/ I'm doing some reflection on how #DDD can help you spot a Platform as a Product Team from @TeamTopologies wrongly applied Image
2/ Indeed, I think we created a Platform Team because the intention was to reduce cognitive load on teams on a specific part.

BUT, on the recent learnings, we think it might be a Bounded Context by itself, a Supporting Subdomain at least.
3/ This is one of the cases in which using different perspectives to the same problem space helps you find the best team composition.
Read 11 tweets
Feb 18
1/ We have been debating with some colleagues about the importance of learning about our decisions within the organization, and how the fast rotation of talent that's happening lately is affecting the decision-making outcomes quality.
2/ Here we had the supposition that the feedback cycle between a decision is made and understanding the consequences are long enough. We always thrive for fast feedback loops, yet we acknowledge that that's not always possible.
3/ It's not the same doing TDD within a unit test - feedback cycle of seconds-minutes vs a business decision and go-to-market strategy that can take months.

We are talking about the latter. Where those business learnings are most valuable for the organization
Read 21 tweets
Feb 17
1/ When you start doing project development, you find yourself with tight deadlines, a lot of tradeoffs in quality, and money spend.

You start feeling that you might be doing something wrongly. You feel that you're not delivering business value

Thread 🧵
2/ You learn about Agile, and why deliver working software as soon as possible. You adopt Scrum, but with a project mindset. So, it's a fake Scrum. It's more like a 2 weeks waterfall.

Yet you adopt a very important ceremony important, the Retrospective.
3/ Based on Retrospectives, you start questioning yourself how are you working. Why can we deliver value to the customer? Why aren't we customer-focused?

You start looking for alternatives.

PRODUCT! PRODUCT-MINDSET!

Just burn the Project Management! 🔥
Read 9 tweets
Jan 13
I share this diagram with other leaders a lot.

It shows that a team goes in different phases and so your leadership style should do.

It's a common mistake to give autonomy to a team that needs direction. I explain the leadership style depending on the team state

Thread 🧵👇 Image
The diagram is based on Elastic Leadership: Growing Self-Organizing Teams.

A 100% recommended book for anyone in a leadership position.

Attached link 🔗
amzn.to/3Gr2TCT
This book has been an inspiration in the way I lead today. Which it's totally based on:

👉 Team stage in the 4 stages of a team
👉 Team context and situation at hand
👉 Team knowledge

As a leader, you adapt your leadership style to the team needs, not the other way around
Read 12 tweets
Nov 6, 2021
We have been practicing #NoEstimates for 8 months. Here are some learnings 👇
We started in a legacy code in which the people that created that service left the company some months ago and we needed to deliver some critical features

No business knowledge, no technical knowledge, a mess ahead

Business: Will you be on time?
Me: No clue yet, give me 2 weeks
Should we go for all the work for 2 weeks, analyze the Job to be Done and come back with an estimation?

We had a very tight deadline, 1month and a half to deliver
Read 19 tweets

Did Thread Reader help you today?

Support us! We are indie developers!


This site is made by just two indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3/month or $30/year) and get exclusive features!

Become Premium

Don't want to be a Premium member but still want to support us?

Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal

Or Donate anonymously using crypto!

Ethereum

0xfe58350B80634f60Fa6Dc149a72b4DFbc17D341E copy

Bitcoin

3ATGMxNzCUFzxpMCHL5sWSt4DVtS8UqXpi copy

Thank you for your support!

Follow Us on Twitter!

:(