Skip to main content

Character and Integrity above all

 How do you lead without stress?  I am finding that many leaders are under a lot of pressure,

not healthy and not sleeping well.  A good leader may have ups and downs but their trust

should never be questioned.  Your day to day work will be hard and require a lot but when

you know you are making decisions with high integrity and treating your employees right,

you should sleep well each night.  

Each day is a new day.  You should begin each day with some quiet time, exercise and

make a plan. 

Then, you do your best that day.  Solve problems, help your team, mentor leaders, architect or

remove toil.

  Above all, do everything with character and integrity because when things get hectic or

when you have to move on, you know you led with trust and integrity.  

People will remember the way you lead more than what you did.  If you are weak in an area,

hire someone to fill that need or go learn more.  This is part of leadership and you will

seldom be fired because you didn't know how to do something.  

Even then, the company may want to bring in fresh new ideas and that is ok. 

You led with character and you will leave with respect and your head held high. 

Please know that sometimes, the company will want to blame you for things. 

The Equafax data breach was blamed on a single

developer by the CEO. 

You should continue to lead and leave with character.  Don't let the world lie to you.  Keep your faith in what is right, true, trustworthy and love people. 

Comments

Post a Comment

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.  
Post a Comment
Read more

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/
3 comments
Read more

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...
3 comments
Read more