Splunk has offered some interesting advice to the channel: don’t bid for all the work on internet of things proof of concept (PoC) projects.
The advice came from the analytics company’s solutions engineer Grey Dziuba, who wrote “For a truly successful PoC, the customer should be in the driver’s seat or at least copilot like a rally car co-driver firing off instructions.”
Dziuba acknowledged that doing so “may not always be ideal and can’t always be accomplished” but recommended service providers should “at least include them in the fun parts.”
Why that division of labour? Because “The fun part is usually where the magic happens and where we differentiate certain products,” Dziuba. “If customers aren’t included, these key components could be perceived as smoke and mirrors.”
“Using Splunk as an example,” he continued, “make sure they are involved in the dashboarding process or at least some key visuals defined in my first point. If all goes well, this moment in the process is when the most wonderful questions start to surface. ‘Can you ….?”
And once a customer asks that question, you’re likely to win more work than would ever be involved in a PoC.
Dziuba offered four other tips for IoT PoCs.
- Outline exactly what the PoC will accomplish in the customer’s environment, because without proper scoping, the PoC often ends up demonstrating that the product only works in a controlled environment;
- Set goals, both so you know what you want to achieve and to prevent scope creep;
- A common topic in the industrial IoT space is convergence between experts in operational technology and information technology. To make sure that happens, make sure all important parties from both worlds are present when the goals and checklists are created.
- Keep PoCs short – weeks, not months, work best, because they show you can get it done rather than stretching a job and requiring more resources for a pilot project.