-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #180 from GSA-TTS/jd-more-project-pages
More project pages
- Loading branch information
Showing
4 changed files
with
61 additions
and
8 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,29 @@ | ||
--- | ||
title: Equity centered design for American Indians/Alaska Natives | ||
description: 10x explored an equity-centered design (ECD) framework for working with American Indian/Alaska Native communities. | ||
hero_banner: | ||
title: Equity Centered Design | ||
subtitle: Participatory design with American Indians and Alaska Natives (AI/AN) | ||
redirect_from: | ||
- /projects/equity-centered-design-ai-an/ | ||
footer: every-solution-starts-as-an-idea | ||
date: "2023-05-05" | ||
slug: "equity-centered-design-for-ai-an" | ||
excerpt: "10x explored a framework for equity centered design with AI/AN communities; the sustained commitment required doesn't align with the 10x multi-phased approach and funding model." | ||
theme: '4' | ||
tags: Projects | ||
--- | ||
|
||
<p class="usa-intro"> | ||
Engagement through an equity-centered framework can help federal agencies shift from "design for" to "design with" | ||
</p> | ||
|
||
Over three phases of investment, 10x explored whether creating an equity-centered design (ECD) framework and guidance could help agencies address challenges of working with American Indians and Alaska Natives (AI/AN) communities and other underrepresented groups. | ||
|
||
The basic idea is that in traditional user research and design practices, the power is ultimately with the designers rather than those who use or are impacted by the product of the design. Despite best intentions, sometimes the result is services that are human-centered, but not particularly equitable in delivery. An equity-centered process/framework calls for a shift in the approach from a traditional "design for" mentality to a "design with" ethos, meaning federal designers center the wants, needs, and expertise of Tribal communities. | ||
|
||
While no one expected that building trust with Tribal communities would be easy, the 10x researchers found that the time needed to build trust was even more significant than predicted. It also became clear that each of the current 574 Tribes required their own frameworks that addressed their protocols, customs, and needs. | ||
|
||
It became clear that given the project's aim for substantial and lasting collaboration with Tribal communities, this work required resources beyond what 10x's current funding structure can effectively provide. | ||
|
||
Despite practical concerns and the recommendation to not proceed with further funding, 10x emphasizes the importance of adopting ECD methods when working with Tribes or marginalized communities. 10x is committed to supporting other efforts to solve this complex problem by making this project's findings, insights and recommendations available to other federal teams taking on this challenge, such as <a class="usa-link usa-link--external" rel="noreferrer" href="https://github.com/orgs/GSA-TTS/projects/38/views/1?pane=issue&itemId=58755623">"Improving Government Digital Service Delivery to the U.S. Territories." |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,27 @@ | ||
--- | ||
title: Low code/no code | ||
description: 10x explored the potential of rapid delivery via LC/NC tools in civic tech | ||
hero_banner: | ||
title: Low code/no code (LC/NC) | ||
subtitle: Uncovering the pros and cons of rapid tech deployment | ||
redirect_from: | ||
- /projects/low-code-no-code-service-delivery/ | ||
footer: every-solution-starts-as-an-idea | ||
date: "2023-02-05" | ||
slug: "low-code-no-code" | ||
excerpt: "There is an upside to rapid tech deployment, but 10x cautions users to consider the compromises in security, maintainability, and more." | ||
theme: '4' | ||
tags: Projects | ||
--- | ||
|
||
<p class="usa-intro"> | ||
10x looked at how LC/NC solutions can help civic tech developers build new tools and apps | ||
</p> | ||
|
||
Low-code and no-code development tools allow users to design and develop applications without needing to know how to code. They can also accelerate development if teams don't have a lot of time to code. 10x researched the fast-growing marketplace for these solutions, as they have gained traction in government in recent years. The team also explored whether there is a need to develop guidance about the use of such tools. | ||
|
||
Agencies are sold LC/NC tools based on the promise of the significant time and budget savings they can provide, and on the ability to empower civil servants to solve their own business needs. But without proper guidance and training, agencies could face compromised information security and struggle with application maintainability due to the endless use of customizations and configurations. A guide on the advantages and risks of using LC/NC tools, as well as how to minimize problems with usability, maintenance, security, obsolescence, and governance could provide a significant value to agencies looking to adopt these methods. | ||
|
||
In 10x's research, however, the team found the promise of LC/NC is often overshadowed by compromises in information security and the related challenges of application maintainability due to the myriad use of customizations and configurations. Another concern was that simplifying design code hides unavoidable back-end complexity, which could also lead to vendor lock-in and higher costs over the long run. The Phase Two team also found there isn't actually an agreed-upon definition of what solutions count as low code/no code, and that makes offering broad guidance difficult for 10x. | ||
|
||
Ultimately, they concluded that the time is not quite right for further funding, but that 10x should revisit this space in a few years when there may be more of an appetite for this type of guidance, and to investigate how LC/NC solutions have evolved to address some of the trade-offs uncovered by the project team. |