Keeping your ear to the ground and following the people behind projects you’ve found useful in the past are great ways to hear about similar technologies in their infancy. It also allows you to follow the platform’s development helping you gauge when you’re confident enough to commit to testing it.
About Sam Jordan
With expansive experience across a wide range of technologies, Sam is the co-founder of Netsells and steers the technical direction of the company, ensuring our team stay at the cutting-edge.
Sam is an advocate for defining the curve of technology rather than following it, researching, testing and integrating the new technologies that allow Netsells to define the space we operate in. He works closely with our internal development teams to turn emerging solutions into commercially viable solutions, allowing us to provide the very best tech on the market for our partners.
Key Takeaways
New technologies don’t only affect development or product, they affect your entire business
Don’t just jump at the newest ‘shiny thing’ if it doesn’t offer a solid opportunity for growth, consider the impact it's going to have across the wider business. Staff will require training, sales are going to have to become familiar and comfortable with the product and marketing will need to make updates across your public platforms.
Remember- tech, by definition, is never ‘complete’.
It is constantly altering to fill new gaps in the market, improve security and offer features that are useful for a greater number of users. Instead, define a ‘complete solution’ based on how well it satisfies your internal requirements. Consider each facet of your business and what your clients need. If the new solution doesn’t have the ability to do everything that the old one could, you will need to run them side-by-side, something that can open you up to a whole host of issues.
Consider Your Existing Stack
Some new solutions may promise things that would make your life slightly easier, but you have to consider the consequences of introducing this to your existing stack. It’s something we see all the time- project recovery briefs where another company has wedged a new piece of tech into an existing process map, with no proper plan for how those systems are going to work together.