I get to talk to a wide range of roles during the day here at Decisions. In the morning I could be talking to an IT executive at a financial services organization in the UK. In the afternoon it could be a project manager at a major hollywood studio here in the US. In between it could be a group call with line of business team members and shared IT resources. The value that Decisions provides truly is different for each one of these people that I get to talk to during my day. And while each understands why they want Decisions – each may not understand the real reason why their colleagues may want Decisions.
This diagram is used to help folks who are new to Decisions understand the difference between the end user experience – somebody who is actually doing their job inside Decisions day to day – and the Designer Studio – the place where you can make changes to the software without writing any code.
Further than that – it’s important to understand “who can” and “who should” be making changes in the Designer Studio. For example – if you work in a bank as an analyst responsible for optimizing lending decisions – then when you log in to Decisions you would only see a few rules that you can change with dropdowns and checkboxes.
On the other hand – if you are an IT administrator who supports the loan processing platform inside the bank and all of its connections to other puzzle pieces in your enterprise stack – then you might have access to all of these designers to add new data types, map new data, change the rule hierarchy your analysts are using, or build a new workflow that connects to the new CRM solution that you are going live with next month.
And then there is the business executive – who wants to understand the process at a high level and its impact on key business measures. Instead of changing rules, or integrating the process with a new CRM – this person wants to see how the rules themselves are impacting the loan portfolio over time. This might be in a report – or even one of our new business models (fancy real time infographics derived from a Decisions Project of workflows and rules – coming in 5.0 this year).
So how does this all come together? I think it boils down a higher level business objective.
When you use software in your business you are making a significant decision. You are choosing to either:
Building discrete processes from scratch with custom code is like creating railroad tracks from gold and then laying them from point A to point B. As soon as you realize you want to get to point C instead of point B – you’ve got to leave the golden tracks you already laid behind and start smelting new parts and laying new tracks.
Purchasing an off the shelf software product is like buying an existing railroad – fully laid – that will get you from point A to point B, but again, when you realize that point C is important your going to need to find some additional railroad somewhere. That might be another product – or that might be more golden railroad (custom code) that you need to smelt and then lay.
Using a platform like Decisions is like having a supplier of railroad parts that are ready to be laid wherever you need to go. You can get to point C faster, and for the same amount of money over time as either of the other options build to point D and E as well.
Even if you can answer the question of where you want to be positioned… you probably realize that will need to change. So how you get there, and what software you use, is going to make the biggest difference in the long run.