| Observations from Country Engagement | @Nabhonil, Roy | Key Pointers Discussed During the Meeting Target audience and intended outcomes - Countries struggle to internalize the concepts owing to the amount of abstraction and confusion owing to nomenclature (IM - Messaging, Registrations, etc.) The attractiveness of GovStack is primarily to the technical community. However, the ground reality is, that without a clearer articulation of business value proporition to departmental heads, it is difficult for it take roots. Issues such as sharing of budget, custodianship of systems, etc. Principles and frameworks are great, but their needs are here and now. So, they want to talk about products. Should we be certifying for compliance of country implementations, and if so, how? And, how do we define success and say that we have arrived at a point where it is safe to say we have delivered impact the GovStack way? With the structured inception phase and the prototyping approach that we have taken in the last few months, the haze is clearing, but it is creating other issues from a product neutrality standpoint. GovStack in principle is a national framework but in action is bottom-up. Hence, unless we initiate two parallel streams of work, where we help them develop tangible solutions in parallel to national policies, and architectures.
|