One Tech Recipe for the Tech Leaders Out There

Problem: So, we all know that big corporates are vulnerable to a bug known as: getting stuck in time and hard to change, this is just a generally accepted reality, so let’s try to debug this.

“Proof of concept” (a fun Hacking term) Fix: So because I come from the tech world, it’s fun for me if I will approach this dilemma using a fun computer hacking method, and let’s call it “Social engineering & Code injection” for now, just to make it fun sounding… and dual value is, you might learn how all the tech dots connect.

“Social engineering” (A fun hacking term):

  1. Observe and Define in your mind who has something to gain from a great new product that can disrupt and change the world.

  2. Observe and Define in your mind who thrives in selling and presenting.

  3. “Exploit” (A fun hacking term) those two elements to galvanise some excitement, by pointing out what kind of epically giant value tech can bring to their customers and therefore their business, which generates passion. Give examples such as Uber, Games like World of Tanks revenue which is bigger than numerous non tech giants combined, Self driving car tech, Electric cars will make going to a mechanic unnecessary, upcoming VR retail, Amazon’s food market moves will make physical food shopping reduce drastically etc.

  4. Because of 1 & 2, you are likely to have easily succeeded in 3. So now the next bunch of challenges come in. Keep reading.

  5. You are unlikely to have the above elements come with skill sets together with any tech delivery skills, so you will need to inject enough tech skills in to those elements just to make them barely useful in tech. This may be tricky but point 3 is helping you here, everyone is excited and wants to change the world. Passion == achieved, so you have good chances.

  6. Draw on the board some typical tech business roles and what they typically do day to day and why and then reference them via some reputable sources. Then try to get the elements 1 & 2 to play those roles (Product owner, Scrum master etc) in a rudimentary fashion. That’s all you need, providing you’re a tech leader, otherwise you’ll need to hire a tech leader who will take the venture by hand step by step.

  7. Now in the point 7 of the recipe you have to know tech or have a tech leader taking the lead. You(tech leader) will need to teach your given elements how to do a product owner job step by step and what a UX expert does, by letting them make mistakes and correcting them via tech logic possible/easy/hard/notpossible method, and turn their usually unhelpful power point and excel sheet presentations in to something that tech finds useful such as industry standard user stories and acceptance criteria, which is routed by a UX/UI expert & tech leader stakeholders.

  8. By this time you will have massive value visually observable by all involved so your strategic credibility is likely to be in good shape, so exploit that and now Teach the elements the point of Agile stakeholder method by demonstrating it in action. This might be tricky because Agile is known to bite elements with incompetency because it expects elements to actually focus on something useful to the delivery of the dream product as opposed to 1 element hiding behind massive amount of different tasks and making themselves appear invaluable while being totally and fully useless to the delivery of the product.

“Code injection” (a fun Hacking term):

  1. At the start gather the username/password for all of third party solutions which will likely be involved because other providers have spent years perfecting their solution which you can make use of. This may be tricky as all big corporates are filled with red tape, so we might need to hack this alone in the interest of delivery and then document them during the delivery, then hand them over at the end. For example: Twilio, Stripe, Paypal etc.

  2. As a tech leader, you need to influence the DB design before the delivery starts in such a way that it will enforce scalability and user stories you have come up with, once you do this, the developers will on the order of magnitude be more clear as to what the user stories are trying to achieve. For example: Table called “all_copy” or/and table called “all_emails” or/and table called “all_settings” <- Getting a pattern?

  3. Typing the code in is cheap (around $28 per hr) but what is hard is tech architecture, so ensure you have a tech architect to bounce theories around with even if you are gods gift to tech architecture, validation is everything. Also involve developers equally.

  4. At all times keep overseeing every super critical element, you have no choice now but to be the glue for everything, such as UX, Product & Tech architect etc., and ensure all decisions and debates are transparent and every developer is seeing them, because you cannot trust managers, they have no use in tech, and they are a single point of failure anyways due to single human memory factor which cannot be expected to be perfect. People don’t need to be managed in tech, management is an obsolete role, agile pin points incompetency instantly because agile roles are well documented.

  5. Set up collaborative task tools and get everyone transparently using agile tools and open communication methods where as much as possible everyone sees all comms, that way nobody can hide in the system.

So there you have it folks, a computer hack usually involves Social Engineering and some code to work, we successfully applied it to the physical world… Thanks for reading!