Andrea Hill (16)
In digital, we pay a transformation tax.
That's it. that's the tweet #fwd50
Great Q in the #fwd50 chat about how we replace tech but culture is more resistant to change. Makes me think about pace layers -
@sboots saying Sean Boots things at #fwd50.
As IT modernization/transformation project costs start skyrocketing, the "transformational" pieces - the part that make services better for users - are the first to get cut. So we end up with expensive products that are only slightly less fragile than what we had before (but not necessarily delivering services better)
Anita Anand mentions there are 30,000 vacancies for digital jobs in the GC. As a former GC-er who moved to the provincial ps, wonder how much flight there has been to other jurisdictions, and if there's any good learnings there... #fwd50
.@acroll referencing salmon ladders in his morning #fwd50 talk. The concrete salmon ladders down the street from my house in BC were recently removed - they'd been thrown up decades ago, and were recently replaced with a more natural envt. Extra metaphor?!
"Governments that abandon an 80-year old lonely man don't deserve our trust" - @acroll #fwd50 [abt blindly following scripts/process and notlearning from/ responding to the impact on real people]
How do we move from directives to dialog? Trusting people to solve the problem in the best way they know how - Great talk by @pahlkadot about not just staying in your lane #fwd50
Do you really need your users to create an online account? Private sector has realized that sometimes it doesnt make sense to introduce that friction. Xiaopu Fung claims that the public sector should be more intentional about when we force users to create accounts #fwd50
Do we consider digital a “discipline” or “a way of working” in government? - Robyn Scott from Apolitical, #fwd50
Government code is littered with comments of "I didn't have the opportunity to get the policy intent clarified, so I made my best guess during implementation". - Jennifer Pahlka, #FWD50 Teams need to be working cross-functionally. Can't just throw business reqts/policy statements over the fence at developers and expect good results