Series: Part 1 – We’re Here for the Business, Not Purity
I’m fed up with architecture being the perceived blocker. I want to help the business build and ship faster, which means the tech teams have to move faster too. This part surfaces the overall scene and some root causes of the mismatches, and offers practical ways for architects and dev teams to work better together.
Part 1.0 – We are here for the business not for purity
Whenever I work for a business, and meet with the customers or with staff wanting cool tech, I want to help them – my mind explodes with ideas and possibilities. I can see a path through the technology options to deliver something quickly. However, over the years, I have been constantly frustrated by the lack…
Part 1.1 — First challenge: Technology doesn’t work
The title is a bit of click bait, but I’m using it to call this out as a baseline challenge. It does not matter what you do, or how you think, or how much money will be spent – the technology underlying your solution will simply never achieve all you want. Every board presentation, every…
Part 1.2 – Second challenge: The Business
Expectation mismatch Quite rightly, the business community doesn’t understand the technology. The icon on a phone screen, and a few pages once the app is open – how hard can it be? The root problem is the orders of magnitude difference between what the user sees vs. the vast complexity required to deliver rich user…
Part 1.3 – Third Challenge: Us – the techies
The final challenging area to delivering at a faster pace technology is – us the technology people. The mindset of techies impacts our ability to communicate with the business – what seems obvious to the developers and techies is not obvious to the business and vice versa. Often the tech community doesn’t help itself, it…