Month: January 2019

January 16, 2019

Greg Thomas

The Morning Crew

The Morning Crew comes in every morning before everyone else, way before everyone else and they kick the day off. They get the engine humming, they light the fires, they turn on the heating, they put the coffee on. They start doing all these things for the team. Then they start going through last night’s issues with the build, responding to customer tickets, setting up the days events, figuring out what needs to be focused on for that day. They start doing all these things for the customer. The Morning Crew, kicks off the day, so when everyone else starts

January 15, 2019

Greg Thomas

To Get New Clients You Need

You need to have a party to get new clients. You need to bring in some food and drink and wow them with an impressive show. You need to bring in industry people to hob knob with and chat about trends and directions. You need to promote this event heavily and make sure people are coming. Or you could put all that time and energy into doing the work. Building the product. Putting it out there. Asking for feedback. Assisting your customers with trial setups. You could put the glitz and glamour aside and focus on doing the grunt work

January 14, 2019

Greg Thomas

Staying on Point

If you don’t have this person on your team, then your team has no direction. When you are not on point – you have no goal, no focus, notdirection, no end state. You have work being done for the say of work being done. Get someone to keep you on point (or even better, become that person).

January 11, 2019

Greg Thomas

Change the Delivery Model

If your project isn’t working, it’s possible that’s not because of the project, but because of the people. No one likes to hear that, after all the “best” people are already on the project, why would we change the people? But are they the right people? Do they know how to call garbage on client requests? Do they understand what development needs to get work done? Do they know what kind of test cases they need to build for solutions being built? Are they willing to step aside to make the project a success? Hint: If they are the right

January 10, 2019

Greg Thomas

Building Community Engagement

Building software for a community is a very tricky thing to do. Primarily because it involves much more than building a product. When you are building for a community you want to be able to engage with them, take feedback on what is and isn’t working and what needs to be there in the next release. Your role takes on more of a “here is our product” to a “here is a product, how can I help you set it up, if you have problems call me, what are your thoughts” kind of implementation. Building for a Community is hard

© 2025 Rambli by Greg Thomas. All rights reserved.