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.
If you’ve been to one of our introductory webinars (decisions.com/events) or booked a demo with us (decisions.com/schedule-demo/) then you’ve seen a diagram like this one:
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.
