Work with them on how to create longer-term business cases
I think integrating the idea of government platforms into regional or local plans could be an actionable first step. These are documents that look ahead 20 - 30 years. I am currently working on the Boston area regional plan for 2050. Most plans have sections relating to "dynamic government". Could be a spot to shift the culture longterm towards new practices.
public forum
What about public forums like G2, Capterra, or Stackshare, how can these be leveraged to share government software insights? Could be framed as open ongoing RFI processes. We should be sharing with each other openly on these platforms. Hope it would at-least improved the level of interfaces / skin vendors put on the same "management" software.
A better philosophy is demos, not memos
Love it!
canonical registers.
The descriptor "canonical" has been very helpful for me to distinguish this data structure from others. Have had a few people think I am talking about something biblical, but it seems to stick. Helps distinguish it from data silos and align it with the other needed components of open standards and APIs.
If you have a government email address, you can create a trial account.
All for it! Built systems allow you the flexibility to include trial accounts.
Purchased web services that have a trail or free tier have been a great place for my digital teams to learn and experiment. I think if the government marketplace had more easy and acceptable options for free or low cost web service trials it would have a major impact on the pace of change.
The justified fears of misspent money should be met with research of "did it work" rather than just rules to restrict behavior.
Developing a collective understanding of what makes a good platform is important. A general rule is that if a system is trying to do multiple things, or is highly customizable, it probably isn’t a good platform.
Love this line. Does this translate into procurement language or is it a best practice norm rather than a rule?