Skip to main content

Learn Anti-Leadership from Basecamp

 There are many different articles out there and Twitter comments about the Basecamp drama.  I am not going to post any here because it might seem biased depending on the article.  Google them yourself.  In short, Basecamp made a policy to not allow political discussions at work.  Coinbase did this previously too and applauded Basecamp for it.  

Apparently, for years there has been a list of funny customer names at floating around Basecamp.  This list or even the knowledge that Basecamp had a list, was disturbing to some employees.  Also, some employees tried to start a Diversity and Inclusion practice.  Despite how much the founders of Basecamp promoted DI, they didn't feel they were being taken serious.  They felt the company was only about the founders and not about employees.   

If this isn't enough, the founders debated and even called out employees for their comments regarding the topics, publicly. 

This is my summary and honestly I didn't fact check any of it because Basecamp is not my real point or care.  I want to talk about leadership policies to drive culture.  

1. Just like each state can have different laws and "cultures" companies should be able to have that too.  This allows employees the right to work at a place that matches their values.  Obviously, safety and equal rights is required but the culture should be able to be different.  Remember this is the private sector.  If you don't like the culture at a company, don't work there or leave. Quickly!

2. Founders or leaders at a company set the foundation for the culture.  You do this with your mission, your vision and most importantly your actions.  Policies are just lazy ways of leadership.  LEAD!!!

3. Hire people that fit your culture you want.  Obviously, the employees that started the list are not the same ones that are there now.  This could be a good thing or bad thing.  

4. Probably the most important, Leaders should take responsibility quickly and directly. I have had several discussions with people and other leaders about interesting people names.  It happens.  A leader has to have a know the mindset of the company.  The employees have to feel they are important too.   The right action was to see the employees no longer viewed the list as funny and address it transparently, plus shut it down.   It is just not worth it to the business and investors.  

5. Relating to number 4, a leader 100% should never publicly shame someone.  I have seen this used too much and it pisses me off.  A leader has to be creative and mindful when they speak or address issues.  This is your job.

As with any leader, I hope Basecamp learns from this experience.

Comments

Popular posts from this blog

2020 State of DevSecOps by Accurics

 This is an excellent report for all IT Pros and Engineers.   Highlights: Storage is most impacted solution Open security groups or network configuration Secrets are not so secret Unused resources are not secure. Take a look at these.  Look again.  These are not highly skilled problems.  They just need guidelines and proactive management.  The article uses policy as code as a solution for many of the problems.  I will drill into each of these more in the future.  I wanted to get the awareness out first and then, come back to solutions.  

Manage IT by Johanna Rothman

I just completed this book. I think it is a really good book which covers a whole lot of software development. This book could possibly be the best book for first time project managers. I believe many of the PMs understand PMM but do not understand software development. This book gives a view of each project role. The only one that it does not cover is Business Analyst or requirements documentation. It does cover QC, development and of course PMs. It gives a PM a view into development processes like TDD, CI and estimation. Many PMs that are new to SD can read this book and get a great start to manager an SD project. If you are a PM or know some, read this book. http://www.jrothman.com/

Matrix Organizations are bad for Software Dev

Development teams need to be teams first and company people second. What happens when your team wants to start using user stories and index cards, but your analyst team manager thinks Use Cases are the best way to document requirements? How about when your QA process is not mature and you keep releasing with defects but the QA manager does not do anything about it? How about your project manager never buys into the team and only cares about being on time and on budget because their review is based on it. Maybe the tech lead wants requirements that never change and never lets the client change their mind. The technical manager taught your tech lead and agrees with everything the tech lead says. Agile or what I like to call "Successful Teams" are teams. They do what it takes to do what the customer wants, deliver features. I am not saying only agile teams are successful but successful teams are agile. If your organization is matrix, get your leadership buy in to override...