As we worked with financial services and insurance companies over the last five years, we saw that these knowledge-gaps at the convergence of design, development and security were something that we could solve with Design Patterns. So we started doing the research.
There are a bunch of different kinds of ‘legacy’ systems which require different strategies to decouple such that an ‘API’ can be provided for a new experience to be built over the top. In this post we are going to look at a set of common legacy system design patterns and how you can tackle modernising them.
Cyber security seems to often be ignored or at best reactive when it comes to business deals, however security has a tangible impact on business value. This is a risk that needs to be understood and mitigated, and can be a source of leverage when you’re on the buy-side or in origination.
This month we have launched a white-paper to get you years more out of your business application investments, while at the same time having employees, suppliers and customers that love the experience of your digital brand.
So if everyone is writing software should you be? What does it take to write software? What is the impact on your business? And hey, while we’re at it, what business are you really in?
Relationships with vendors don’t normally start as difficult. They devolve into difficult situations and are ultimately a result of the behaviours and needs of both parties in the relationship being unmet.
So how do you see the warning signs early? How can you deal with vendors once they have officially become difficult?
As we have seen in other blog posts, bespoke software development for any business carries with it great risks – many of which can often be unknown to the business. That is not the point of this post! This post is about risks that are known to the business, yet they remain ignored and without a plan for mitigation, leaving the business in a world of hurt – unprepared and reactive at the moment least expected.
The potential returns of investing in or acquiring startups can be phenomenal. The problem is that pretty much every business worth investing in has some kind of software at its core giving it the competitive edge. Why is that a problem? Any bespoke software has debt associated with it: technical debt.
The due diligence process can be a challenge. Looking under the covers at the finance, operations, talent and assets of any company is no small task. Once you add technology into the mix it creates a concoction which can give unexpected results.
What are the things you’re looking for when performing technology due diligence on a business?
Intellectual Property (IP), Talent, Security and Costs