It's a Thursday, and all week, you've heard rumblings about this new technology that people seem to be really excited about. Your manager asked if you'd heard about it yet, and they sang its praises, talking about how it could totally change your industry. What started as a sense of excitement started to shift in the air. It subtly seemed to shift from excitement to worry; there were brainstorm sessions being scheduled to talk about how this new technology could be incorporated into existing processes to improve them. There were contests to see who could come up with the best idea, and then, when nobody seemed to participate because the prize was kinda lame, there was an open box of sorts for ideas to be submitted whenever they struck.
A couple of weeks go by, and the rumbling seems to have died down, with a few folks still seeming pretty excited about this tech, but that seems to be it.
Then, you're sitting in a meeting with your manager, talking about career development, and your manager says, "I'd like to offer you a bit of a stretch assignment. You know that tech everyone was talking about a few weeks ago? It seems like a lot of vendors in this space are already adopting it and offering it in their solutions. I want you to go out there and see what exists, and come back with recommendations on what we should buy to try out for our own team. Can you take this on for the next few weeks and, say, in a month, come back with some initial thoughts?"
Great, now what?
Setting yourself up for success
- You have a problem to be solved and criteria about what a good solution should include. This becomes the basis of your scorecard for any technology you decide to test.
- You have expectations of the tech that you can describe to a salesperson. This makes sales' job easier because they will know how to cater their demo to you so that it's relevant. This makes your job easier because you won't have to wonder if anything the salesperson is showing you would actually be useful to you or any of your peers.
- You have narrowed down the type of project you could use if the vendor offers a pilot study for you to test the tools. If you can use a project that was run previously with a trusted vendor, you can compare the experience, including the data quality, the speed, and the call-outs that made up that wish list for improvements to the project flow.
- You have peers who can be involved in the tool evaluation who will be using this tool, so they can get to know the tool and provide feedback before any decisions are made on whether or not to purchase the tool. This gets their buy-in much earlier in the process and makes change management easier down the road.
- Your recommendations for tools that use this fancy new tech will actually be relevant to your team, making excellent use of budget and resources.