Know Your Use Cases
I have been there, “I have a problem and DO NOT know how to fix it”, let alone knowing what the problem really is. Consulting seems to always be like that. There have been times that we know what we want, but not how to get there, worse, there have been times that we have known how to get there, but don’t know what we want! Engineers are so sure, aren’t we?
One day you get contacted by consultants. They want to help, but also like hours! Billable-hours, they call, email, follow you online. You know they can help, but not directly. You don’t even know what you need! Know your use cases! There are ways to figure out your use cases without starting a project. I have seen it way to many times, let’s get started.
What if you don’t know
That’s okay! Not knowing your use cases is fantastic, probably better because someone like me can tell you exactly what you need. Nothing more, nothing less. I’ll get a chance to show you what I’ve seen here, there and other places. Chances are someone has solved this problem before. Easy path isn’t always the best, but the best path is easy. Trust is key, trust in others who’ve done it before.
People can tell you for sure, but they’ll want an engagement. They can imagine what you need. Most customers aren’t all that different after all, are they? Each step of the way is different for some reason. I still can’t wrap my head around that, but I have a solution.
“Oh no that’s an issue and need to be fixed now!”
- Where are you?
- Where do you need to be?
- What is in the middle of all that? – I think (We’ve done this before….)
- What’s the cleanest path?
Well, we need to talk about it. If it’s a massive amount, you may need advisory services. There is nothing worse than thinking you need exactly this and that, you spend tons of time and money solving it, then move onto the next thing that then makes what you just did obsolete! How would you ask for more? How can we get to where we need to be? The goal is not so simple. Let’s face it, no company wants to spend hours figuring out your requirements, only to then be told, it’s not in the budget. Think about tech projects as a partnership. A two-way street, you need expertise, they need hours. Plain and simple hours. What kind of hours? Consistent hours.
What if you do know?
let's take a look at your technology
I have to say some products just simply require tons of time to get anything accomplished! I don’t know if I like or dislike that as a consultant, but I know there’s a difference. My motto has always been, there’s more work to do, let’s make it simple. Point and click might be just too simple, or exactly what you want!
- I don’t have anything!
- I’m locked in and in love!
We need to make sure you get this! I’m personally an expert in a few things and there’s nothing better than having flexibility! You want something, we got you and here you go! Or - I love this, however there’s a challenge.
What is the timeline?
Sometimes timeline is everything. You want things done, you have time for 2 or 3, what do we do? I would suggest taking an approach where there’s a bottom line. “Bottom line, I need people provisioned to AD if they are an employee”. Done, that’s direct, understandable, measurable and something that we can take as a win.
What is the budget?
Having a budget in my mind makes you the MOST powerful negotiator! “I have a certain amount and I’m getting what I want”. This disposition, 1. Get’s you what you want, but 2. Allows for more! If I could, I was looking for help, I knew the dollar amount it’ll take, I have authority to sign, and it’s clear. It’ll happen right on time. These projects always go well. If there’s a miss, fine, let’s adjust, move on and perhaps, just perhaps we are a few days late. Our final negotiated date of completion was weeks later anyway. Success!
In-house or Consultants?
The truth is, whether you lean on your internal team or bring in outside experts, the journey to a successful tech project hinges on clearly understanding your use cases. For in-house teams, this means taking the time to deeply analyze needs before diving into solutions. For consultants like myself, it’s about guiding clients through the discovery process, building trust, and ensuring we’re solving the right problems in the most efficient way possible. Ultimately, it’s a partnership built on clear communication and a shared understanding of what needs to be achieved. Define your use cases, be realistic about timelines and budgets, and you’ll be well on your way to a positive outcome, no matter who is executing the work.