Info | Link | Summary | To be considered | Comments |
|---|
Design with Users
Workflow and Design Principles for UCD and Design Thinking | https://digitalprinciples.org/principle/design-with-the-user/ | Focus on who needs to be involved and user testing. Incorporate multiple user types and stakeholders Improve current processes Develop context-appropriate tools based on users needs and feedback - accepting that digital solutions are not always the best fit for a problem Create user personas. Develop user personas that include names, pictures, demographic characteristics and motivations. Develop and validate user scenarios. Using insights from the user personas and business processes, create user stories to describe simply and clearly what users need the tool to do and why they need it. Set expectations with users and stakeholders you involve. Beta test the tool or system with a larger group to confirm readiness for wider deployment.
| | Possible content for the onboarding page |
Understand the existing eco-system
Ecosystems are defined by the culture, gender norms, political environment, economy, technology infrastructure and other factors that can affect an individual’s ability to access and use a technology or to participate in an initiative. | https://digitalprinciples.org/principle/understand-the-existing-ecosystem/ | Coordinate with other implementing organizations, civil society and the government Ensure the technology aligns with the existing legal and regulatory policies Monitor the ecosystem for changes throughout the project lifecycle, and adapt your products, tools or initiative as needed. People: What are the target users’ levels of education? What digital tools are they familiar with? Map out current and past digital development initiatives. Understand the local protocols you need to account for and adhere to. Evaluate for intended and unintended outcomes, as well as other contributing factors that may account for results. Monitor for and document contextual elements that either facilitate or impede implementation.
| | Could be relevant in the future for the contextual panel. |
Build for sustainability A program built for sustainability is more likely to be embedded into policies, daily practices and user workflow. | https://digitalprinciples.org/principle/build-for-sustainability/ | Plan for sustainability from the start. Build a program that can be adapted as user needs and the context change. Continue to review your design as you implement Identify additional resources needed to sustain the initiative Identify indicators that can help measure sustainability. For example, evaluate whether the tool or platform saves users time or effort, as these indicators drive the likelihood that the tool or platform will be used over the long term.
| | Could be relevant for the onboarding page but not quite sure where to put it. |
Be Data Driven
The data produced by a digital initiative should be used for more than just outputs, such as published work or donor reporting. | https://digitalprinciples.org/principle/be-data-driven/ | Design programs so that impact can be measured continuously and incrementally, focusing on outcomes, not just outputs. Make use of existing data, including open data sets and data from interoperable systems. Use rigorous data collection methods. Consider and address potential biases and gaps in the data collected, perform data quality checks, and maintain strong documentation behind collected data. Create a data use culture Be holistic about data collection and analysis Collect and use data responsibly Adopt standards to guide data use. Link Consider data transmission and storage needs. Develop automated processes for data extraction, preparation, analysis and reporting so that information is quickly usable, meaningful and available to decision makers. Gather baseline data on your indicators, and regularly analyze data to measure impact and outcomes Develop a data analysis plan. Map out how the collected data will be organized, classified, compared and displayed relative to the evaluation questions, as well as how multiple data sources will be integrated.
| | |
Use Open Standards, Open Data, Open Source, and Open Innovation | https://digitalprinciples.org/principle/use-open-standards-open-data-open-source-and-open-innovation/ | Nothing relevant | | |
Reuse and Improve Identify relevant methods, standards, software platforms, technology tools and digital content that have already been tried and tested | https://digitalprinciples.org/principle/reuse-and-improve/ | | | |
Adress privacy & security | https://digitalprinciples.org/principle/address-privacy-security/ | Keep the best interests of end users and individuals whose data are collected Assess the risks of unauthorized access or leakage of any stored data. Understand that risks are highly contextualized, not just to countries but also to communities, populations and periods of time. Minimize the collection of personal identifiable information. Be transparent with individuals whose data are collected by explaining how your initiative will use and protect their data. Obtain informed consent prior to data collection. It is crucial to ensure that participants understand why their data are being collected, how data are used and shared, and how the participants can access or change the data collected — and that they be given the option to refuse to participate.
| | |
Be collaborative | https://digitalprinciples.org/principle/be-collaborative/ | Understand how your work fits into the global development landscape. Document work, results, processes and best practices. Define how your project will contribute locally. Design your solution collaboratively with end users and other partners. Present your initial design to other practitioners for feedback. Share your failures to help others avoid making the same mistakes.
| | Possible content for the onboarding page |