#digitalgov

Cloud reception is expanding quickly to speed up IT modernization. IT spend on cloud is relied upon to develop over multiple times the overall IT spend planned generally. Cloud governance is a central component for cloud reception to scale and be effective. Cloud reception without cloud administration prompts disappointment. This article clarifies the significance of cloud governance for successful cloud reception and explains the different components of cloud administration.

Cloud governance is the framework coordinated towards controlling business exercises by giving information security, information to the executives, and approved admittance and modification of data to keep away from functional and monetary misfortune. It likewise aids hazard the executives related with distributed computing. Cloud governance gives the arrangement of standards to the administration for the powerful and productive working of the framework. It empowers the accomplishment of the targets of the association. The proficient usage of assets helps in the decrease of the expense.

Governance Policy in Cloud

The cloud is helpless against different dangers created in the innovative climate. There is a need to control these dangers. The administration strategy gives an administrative system to the undertaking, controls, and screens any deviation from the authoritative objectives.

The governance strategy works with hazard the board. It advisers for accomplish the business goals without compromising the investors' necessities. It empowers the ideal use of the cloud foundation. Administration strategy guarantees that the administration is responsible, viable, and consistent with the system. The strategy alludes to the guidelines of working stages, applications, exercises on the working stage, working frameworks, and distributed computing essential help models.

Key Components of Cloud Governance

Cloud Business Office (CBO) guarantees the arrangement of cloud vision with business vision and guarantees that administration is enforced across the undertaking. CBO is additionally answerable for requests to the board, cost advancement, and prioritization.

Cloud governance association design and jobs and obligations.

Cloud governance measures around the cloud service lifecycle.

Cloud primary parts like cloud reference engineering, principles, layouts, rules, best practices, and strategies.

Principles of cloud governance

Compliance with strategies and norms: Cloud utilization guidelines should be predictable with guidelines and compliance principles utilized by your association and others in your industry.

Arrangement with business goals: Cloud procedure ought to be a necessary piece of the general business and IT methodology. All cloud frameworks and strategies ought to verifiable uphold business objectives.

Joint effort: There ought to be transparent arrangements among proprietors and clients of cloud infrastructure, and different partners in the important organizational units, to guarantee they make suitable and commonly valuable utilization of cloud assets.

Change the board: All progressions to a cloud climate should be carried out in a reliable and normalized way, subject to suitable controls.

This week, our team is celebrating a few huge wins!

We finally presented a (beta version) of our insights report to our core team this week. 

It’s currently a monster 155 page document since we had so much rich data from our deep discovery phase! Now that our analysis is complete and fully documented, we can draw from it to present to various audiences and - most importantly - use it as the basis for building out prototypes of our product!

Here’s a sneak peek at some slides, demonstrating the breadth of what’s covered in this report: a journey map that more accurately demonstrates the ways that applicants to MSP engage in the various touchpoints throughout the process; exploring the purpose behind certain steps and demonstrating where understandings are shared or divergent; and explaining how code can be used to streamline the process to be more opinionated in the way we collect data. 

We’ll do a deeper dive into our research in another blog post soon, but for now, just know we’re pretty amped about it!

Another long-time-in-the-making milestone this week was finally getting set up for a trial instance with Apply by SurveyMonkey. 

This is the Software as a Service (SaaS) solution that we’ve been leaning towards, and now we finally have an opportunity to play around with it - ie. the design, build, test part of our fellowship! We are so excited to be able to show staff more tangibly how digitization of the MSP program can improve the applicant experience, while making their own lives easier, too.

So far, Adam’s been exploring how to create different projects within it...with some existential dummy data (very On Brand for him). 

The final big milestone we hit this week was the official receipt of the Options and Analysis that had been initiated some months back by Health Canada Corporate Services in order to determine which back-end system we’d be integrating with. As you’ll know if you’ve been following our project, we are now pushing for an end-to-end solution - Apply - but it took us some time to convince Corporate Services that this was the right direction. The Options and Analysis documentation is the first step in having them support us to go in this direction and perhaps socialize SaaS solutions more broadly throughout Health Canada, when appropriate. Fingers crossed!

And, on that note, we are going to finish our big week off right by heading out for a drink together. Team building and celebrating successes are important, ya know?!

Hello! You haven’t heard from us in a while because we’ve been focused on publishing our first official Code for Canada blog, were at our first Code for Canada Fellow retreat, and have been absolutely drowning in data. But these are all good things!

Code for Canada Fellows goofing around at our first retreat. 

We wanted to give a quick check-in on where we are with our discovery research and data analysis, so you know why we’ve been quiet.

During the UX research phase, we completed:

More than 30 hours of interviews, including with past, current and potential applicants, staff, and stakeholders

Two design probes breaking down the Letter of Intent template

Analysis of the contents of the PSD inbox, which is often the first point of contact for applicants interested in the program

Observational studies of PHAC processes and ways of interacting with applicants

Slide from our most recent Project Panel presentation, where we gave an update about our work, including our UX research process.

As you can see from the walls in our office (and even the filing cabinet), where more than 500 are posted, this has given us at least a thousand data points! We’ve been working hard on collating, synthesizing, and analyzing that data. My dog, Boris, helped.

My sweet dorkie (no, actually, that’s his breed) dog dorking out with us during data synthesis.

Rose working on analyzing our data points, which have spilled over from the walls to the tables and filing cabinets. Oof.

In the next week or two, we’ll be delivering an insights report that identifies key areas of opportunity to streamline the MSP program’s application process for users, as well as make it more accessible to the types of innovative organizations across the country that it intends to serve.

Our team is working on a project about making data accessible, primarily to new users outside the National Energy Board of Canada. Right now a lot of information is wrapped up in layers of legalese and a crunchy database which can make finding information very difficult for those without training. This is workable for many users but can create a pretty big hurdle for those who lack expertise in the area. At this point in the project we’ve only just begun to tackle this problem and although we know that there are problems, their definition is still a bit foggy.

To get a better idea of where and how we should be focusing our efforts we’re pouring over documents, cramming our calendars with meetings and info sessions and talking to as many people as we can get our hands on.

One thing we’re doing to explore our users is stakeholder mapping - this is to figure who’s involved with what we’re working with, what their relationships are with each other and what problems and successes they encounter while trying to use NEB services. This is a way us to establish a baseline for the present moment and figure out where and how we should be moving forward.

Government has a really big user base which can make user research a bit difficult. A big reason for this is that governments should work for everyone, thus it can be difficult for our team to get a foothold a specific area. This is the difference between a problem which such as “IKEA wants to design a new children’s chair” where users might be children with rooms whose families buy furniture, and the kind of problem we’re dealing with which is more like “regulatory information within the NEB’s filing system is difficult for many people to access” where users include workers inside the NEB, indigenous people, governments within and outside Canada, researchers, students, lawyers, NGOs, landholders, journalists and others.

Right now we’re working on this problem by pouring over documentation of past engagement and engagement roadmaps to understand what users have said in the past and get a better idea of where we’re starting out from. This can also help us understand what issues might exist before we go in, which helps us construct our research plan.

The point of this isn’t to jump headfirst into user research yet - it’s about figuring out who we might be talking to down the line and what their needs are.

We’re also talking to stakeholders internal to the NEB to understand existing structures and relationships. So far we virtual piles of documents and plenty of webs mapping out stakeholders, troubles we know they’ve had in the past and plenty of extra info. As we conduct internal stakeholder research and develop our outreach plans we’ll know who to go to talk to on the outside.

Stay tuned for an upcoming blog about design research methods! We’re still running research sessions so it should be out in the next two weeks. ---------

Notre équipe travaille actuellement sur un projet visant à rendre les données accessibles, principalement aux nouveaux utilisateurs extérieurs à l'ONÉ. À l’heure actuelle, de nombreuses informations sont regroupées dans des couches de jargon juridique et une base de données croustillante, ce qui peut rendre très difficile la recherche d’informations pour les personnes sans formation. Ceci est réalisable pour de nombreux utilisateurs mais peut créer un assez gros obstacle pour ceux qui manquent d'expertise dans le domaine. À ce stade du projet, nous venons tout juste de commencer à nous attaquer à ce problème et, bien que nous sachions qu’il ya des problèmes, leur définition est encore un peu floue.

Pour avoir une meilleure idée de l’endroit où nous devrions concentrer nos efforts, nous concentrons nos efforts sur des documents, en remplissant nos calendriers de réunions et de séances d’information et en discutant avec le plus grand nombre de personnes possible.

Une des choses que nous faisons pour explorer nos utilisateurs est la cartographie des parties prenantes: c’est pour déterminer qui est impliqué dans les projets avec lesquels nous travaillons, quelles sont leurs relations réciproques, ainsi que les problèmes et les succès qu’ils ont rencontrés en essayant d’utiliser les services de l’ONE. C'est une façon pour nous d'établir une base de référence pour le moment présent et de déterminer où et comment nous devrions aller de l'avant.

Le gouvernement dispose d'une très grande base d'utilisateurs, ce qui peut compliquer un peu la recherche sur les utilisateurs. Une grande raison à cela est que les gouvernements doivent travailler pour tout le monde. Il peut donc être difficile pour notre équipe de prendre pied dans un domaine spécifique. C’est la différence entre un problème tel que «IKEA veut concevoir un nouveau fauteuil pour enfants», où les utilisateurs peuvent être des enfants avec des chambres dont les familles achètent des meubles, et le type de problème auquel nous sommes confrontés, qui s'apparente davantage à «des informations réglementaires au sein de la société». L'accès au système de classement de l'ONE est difficile pour beaucoup de gens », où utilisateurs comprennent des travailleurs à l'ONE, des peuples autochtones, des gouvernements à l'intérieur et à l'extérieur du Canada, des chercheurs, des étudiants, des avocats, des ONG, des propriétaires fonciers, des journalistes et autres.

À l’heure actuelle, nous travaillons sur ce problème en fouillant dans la documentation de l’engagement passé et des feuilles de route de l’engagement afin de comprendre ce que les utilisateurs ont dit dans le passé et d’avoir une meilleure idée de l’origine. Cela peut également nous aider à comprendre quels problèmes pourraient exister avant d'entrer, ce qui nous aide à construire notre plan de recherche.

L’intérêt de ceci n’est pas de s’impliquer à fond dans la recherche sur les utilisateurs: il s’agit de savoir à qui nous pourrions parler et quels sont leurs besoins.

Nous discutons également avec les parties prenantes internes à l'ONÉ pour comprendre les structures et les relations existantes. Jusqu'à présent, nous avons des piles de documents virtuels et de nombreux sites Web répertoriant les parties prenantes, des problèmes que nous savons avoir rencontrés dans le passé et de nombreuses informations supplémentaires. En effectuant des recherches internes auprès des parties prenantes et en élaborant nos plans de sensibilisation, nous saurons à qui parler à l'extérieur.

Changing the Knowledge Management Tides and Why it Matters: The Federal HR Wiki

Imagine this – a go-to member of your organization just retired, a furlough is approaching, and now no one knows what to do. What communications need to go out?  Who is considered ‘excepted’?  Can the daycare center stay open?  In the absence of mind-melds, how do you make expert knowledge easily accessible to newer team members? The Strategic Initiatives Group (SIG) at the National Institutes of…

The Essentials of an Editorial Calendar

Anyone engaged in content marketing or content production probably owns a robust editorial calendar. A calendar that is quickly updated, helps keep deadlines and is flexible can serve as a helpful blueprint of your content activities for the year.

At USAGov we cover a lot of topics and partner with many agencies. Having an editorial calendar has helped us in a variety of ways, from staying on top…

GAO to Congress: Federal Agencies Are Making a Difference Through Open Innovation

Federal agencies confront tough problems everyday. In searching for solutions, agencies will want to attract different perspectives, test new products, build capacity and communities, and increase public awareness.

How do they do it?

The answer: open innovation.

Federal agencies need to engage and collaborate with all sectors of society, a task made easier by online technologies, says a…

Dear Search: Reading Between the Lines of Search Data

Welcome to the first Dear Search article, an occasional series where the DigitalGov Search team addresses common search questions.

Dear Search,

Right now, I am building up user research services that can be offered to product owners on a regular or as-needed basis. So, being able to look at search trends and offer advice to teams seems like a good start.

When you are trying to understand user…