So many organisations today struggle with their data. The world of big data, analytics and predictive modelling is so attractive, yet, the perceived complexity of achieving a data nirvana is so great that data projects either spiral out of control or never start. So how can you get a handle on your current data, whip it into shape and start using it?
No matter what industry you’re in, you have to deal with complexity on a daily basis. From the complexity of computer systems you use to get work done, to the complexity of the projects you’re managing – it seems a byproduct of the information age is complexity.
More often than not when engaging a software developer there will be a conversation about price:
“Here is what I want. How much will it cost?”
The conversation may be more subtle, or nuanced, but the bottom line is pretty much the same no matter what: A true definition of what is actually being asked for is not very well defined at the point in time a price is being requested.
Where can you go from here?
I started working on different approaches to corporate education and training with Thinking.School in 2016. Initially, I started developing a program that was quite abstract: It was set up around ‘thinking strategies’ and how they could be used in problem-solving. The problem with abstract training like this is that we end up with a metaphoric hammer looking for a nail. It was a set of strategies looking for problems to deal with. More interesting, I found is that this problem with abstraction in training is not unique. As I spent more time working in the space and talking to others, I saw the same issue plague enterprise scale Design Thinking programs – they make sense, they sound great, people enjoy them – while they have pockets of influence, they struggle to have a broad lasting impact.
Humbled that our ongoing research into Secure UX design patterns is being featured on The Cyberwire.
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?
The Dealmaker’s Guide To Tech Risk
Four questions that reveal insights into any software business to mitigate your risk.
Level 25, 88 Phillip Street
Sydney
NSW 2000
Australia
©2003-2018 Pixolut Pty Ltd trading as Thinking.Studio
All Rights Reserved