Articles for category: Leadership

April 10, 2023

Greg Thomas

Be Your Team Culture

Don’t talk about it. Don’t do a post on it. Don’t evangelize it. Don’t youtube it, instagram it, snap it, tiktok it. Definitely keep it off of LinkedIn. Just be it, live it every day, and embolden your path and those around you. Remind yourself every morning what it is, and hold yourself to that standard. You won’t get as many likes, you might not get people flocking to your job portals and it probably won’t make the news but it will matter to the people it needs to matter to the most – your team, and that’s all that

April 9, 2023

Greg Thomas

Are you Coachable?

We all say we are. But we aren’t. In some aspects we want to be coached, but only up to a certain level. And yet, when things go wrong the first thing we say is – “It’d be nice if I had someone helping me”. So what’s it going to be then?  Do you want to be coached so you never have to say that or do you want to keep saying you’re coachable but not letting it happen?

April 7, 2023

Greg Thomas

Forget the Optics

If you’re delivering your work and leading your team. Don’t worry about the things you miss. Focus on what it does and how your team is doing. You don’t need to have the flashiest presentation to look the best if you aren’t delivering anything behind it. The optics always take care of themselves.

April 5, 2023

Greg Thomas

What Matters Next?

This is another question that a Dev Manager should always be working on in the background in anything they are doing. What matters next? Talking to QA, PM, and other development teams – the goal is to get ahead of what needs are coming at the team next and ensure that it is prioritized and laid out for them in a way that matters and a way that they can be successful. It’s not the team’s job to know the answer to this question, it’s the Dev Manager’s to have it answered for the team to act on.

March 30, 2023

Greg Thomas

How close to Release are you?

The Dev Manager should always have this number in the back of their head.  They should always be working towards it. They see the big picture, they see how the requirements are flowing in, they see how QA is testing, they see how things are working, what is doing well, what is doing poorly, what is slowing down the team, and where they are excelling. They should always have this number in their head + 1. The “+1” is their own internal buffer, it could be a week, a sprint, a month – whatever metric they have, it’s “+1”.  The

© 2025 Rambli by Greg Thomas. All rights reserved.