A systems look at the variables in a successful SaaS product
A while back I shared a version of this rough and ready systems diagram looking at a system to manage new product development priorities where the situation of interest is the need to create new revenue streams to diversify. Note: It doesn't fully follow the conventions of Systems dynamics and is firmly grounded in a B2B SaaS context. This formed the basis of a Systems Thinking assignment that I did, so sharing a bit more here in case anyone has any comments or suggestions on my exploration of this space. It kinda felt right, yet the focus felt it was off. So, I then used the 12 boundary questions from Critical Systems Heuristics ( CSH ) to think about the system again from other viewpoints. Source of in fluence Who should be the stakeholders? What’s at stake? Stakeholdings: constraining or developmental? Motivation (beneficiary) Business owners Business sales team Software users (purpose) Maximise profits from customers Solve the business problems of t...