You are currently viewing Too many meetings? Read this.

Too many meetings? Read this.

Want your data to continue to be a sh!tshow?

Just dive in and don’t talk about it up front.

Recently, I had a client express, “We’re having too many meetings. Can we please just do the thing and move on?”

I politely suggested that we’re near the end of all of the meetings we need to have to do this right. There were certain things we needed to tighten up before integrating the client’s two systems so we didn’t integrate them wrong and have to clean up a clusterf!ck of data issues later by not planning right first.

I get it, I hate having too many meetings, too. I wrote a whole post about that.

But to properly plan integrations and data migrations, to all agree on what needs to be done before the thing gets done is really important. If you don’t do that, you end up with dirty data and poorly integrated systems.

So when the project lead at this client’s organization emailed me to ask if we can please stop having meetings, I asked them to call me. I told them, “We’re almost done with meetings – we just need to do a couple more things.” We ended up meeting all together the next week and everyone on the call, including the project lead, said, “Thank god we’re having this call. We wouldn’t have thought of this or that, we didn’t realize that’s how this worked.”

There is part of any transformational project where you need to talk a lot at first.

At StarSpring, we take a people-based approach to technology where we don’t care what your systems are at first but we care a lot about your processes. There’s a method to the madness. We first figure out the job you’re trying to do and then choose the best tools for it, making sure to think about all the data points we need to migrate over to the new system so it’s clean when it gets over there. Otherwise, you’ll spend countless hours of manual work unf!cking up the data you’ve f!cked up in the new system. I’ve seen this go wrong so many times, and it always falls on already overworked frontline staff to do the costly, error-prone, monotonous cleanup. And even still, sometimes the data cleanup doesn’t happen correctly and you end up dealing with the aftereffects for years to come.

Knowing up front that I hate useless meetings and have a good handle on when we need to have one or not, trust the process when it seems like one or two too many meetings. We need to talk so you don’t end up with a cesspool of bad data later and a huge headache for your people. Just like any relationship, when we communicate about these things early on, it’s an awful lot smoother later.

So: Want your data to continue to be a sh!tshow? Just dive in and don’t talk about it up front. Want to not have these problems and do it right? Call us.