# Navigating Accessibility through Cooperation: A Closer Look at Powerhouse Workflow

Our mission is to make Atlas accessible through cooperative efforts.

Thus, the purpose of this post is to provide you with a clear understanding of the Powerhouse Process Implementation Workflow to foster stakeholder engagement and by extension Atlas accessibility.

Here's what we're aiming to accomplish by breaking down the essential steps of our workflow:

**i) Easy Spotting of Cooperation Opportunities:** We've mapped out our workflow to identify where stakeholder engagement is most valuable and needed.

**ii) Illustrating Connection with Atlas Accessibility:** Our work isn't in isolation; it directly dovetails into the bigger idea of making Atlas more user-friendly.

In the upcoming sections, we'll begin by introducing our Process Implementation Workflow, giving particular attention to the initial two steps. We believe - at this point - that other steps might not be as significant in terms of cooperation, as compared to the first two: Needs and Business Analysis. Each step of our workflow entails both the *Cooperation Opportunities* for stakeholders (e.g, AVCs) and how these joint efforts translate into *Atlas Accessibility*.

Fig1: Powerhouse' Process Implementation Workflow

## 1. Cultivating Systematic Cooperation

The Powerhouse team believes there is a lot to learn by tapping into the collective wisdom of stakeholders like AVCs to help refine our development approach and ensure a resilient and impactful productization of the endgame operations.

We recently met with Sovereign and Regenerative Finance AVCs, introducing our comprehensive Process Implementation Workflow; you can access the detailed presentation [here](https://docs.google.com/presentation/d/1uJWenIgzCVnvm5hWsV81UdZxeuXB5ApKtLZov3bCBI0/edit?usp=sharing).

Drawing from these combined inputs, we present a robust way of cooperation and how this directly translates into enhancing the Accessibility of Atlas.

Looking ahead, the potential role of AVCs is in enhancing quality measures. They can pinpoint areas needing quality control, uphold process standards as auditors, and serve as liaisons between stakeholders, ensuring the software remains in tune with community needs.

### 1.1 Needs Analysis

Needs analysis is all about figuring out what's most important when it comes to automating processes. This involves finding, naming, and ranking the top needs. Experts, the community, and project limits all play a part in this decision-making process. By taking all these viewpoints into account, needs analysis helps us make smart choices about how to make processes smoother and more efficient through automation.

#### 1.1.1 Cooperation Opportunity

##### 1.1.1.1 Requirements Elicitation and Feature Prioritization

The essence of this step is to gather a lenghty list of ideas and condense it into a consise set of top priorities.

AVCs' input is instrumental in uncovering, defining, and prioritizing essential automation requirements. We've established a feature board ([here](https://powerhouse.frill.co/b/j0xd92vq/feature-ideas)) where AVC members and other stakeholders can contribute by voting on diverse features.

###### Fig2: Interactive feature prioritization board

Your feedback will help inform our prioritization decisions, ensuring our efforts align with community needs.

#### 1.1.2 Atlas Accessibility

By collectively identifying key needs, this approach ensures that the most critical aspects of processes are highlighted and prioritized. This mapping results in streamlined and efficient workflows, which in turn contribute to the accessibility of the Atlas. When processes are well-structured and intuitive, navigating the Atlas becomes more straightforward for users.

### 2.1 Business Analysis

Business analysis is a dynamic process that revolves around comprehending an organization's requirements and putting forth viable solutions. It encompasses multiple key components:

**Process modeling**, for instance, involves visually mapping out workflows, thus refining operations and boosting overall efficiency.

The first example, known as SimpleExpenseReporting, demonstrates a [permissioned process](https://www.notion.so/makerdao-ses/Permissioned-Document-Processes-30406507344648618442afc570e384f4?pvs=4) involving Core Unit Administrators. They initiate the process by uploading Budget Statements in a Draft state, which can later be transitioned to the Final state. The permissions are set to prevent editing of Budget Statement documents after they are finalized, ensuring accuracy. The associated state diagram illustrates the flow, with the process beginning from an implicit External state and progressing through Draft and Final stages.

###### Fig3: Simple Expense Reporting: State and Transition Labels

The second example, AuditedExpenseReporting, builds upon the Simple Expense Reporting model by introducing the role of Core Unit Auditor.

###### Fig4: Audited Expense Reporting: State and Transition Labels

At the same time, **conceptual wireframes** are developed, offering preliminary design concepts that play a pivotal role in guiding well-informed decision-making.

###### Fig5: Conceptual Wireframe for dedicated Milestone Roadmap Overview page

The wireframe above depicts a solution to the problem of stakeholders facing difficulties in comprehending the progression of endgame work due to a lack of structure and documentation. By visualizing this organized presentation, stakeholders can effectively track and understand the advancement of endgame phases.

Additionally, the systematic approach of creating **document models** captures the intricacies of business logic. The document model comprises three key elements: the document's current state, its history of operations, and a processor. The state represents the latest version of the captured business information, operations chronicle modifications made over time, and the processor enforces the business logic.

###### Fig6: Document Model Structure Diagram

These models serve as a fundamental framework for analysis, forming a solid foundation and fostering enhanced collaboration between the professionals responsible for business analysis—analysts—and those responsible for turning these insights into reality—developers.

#### 2.1.1 Cooperation opportunity

##### 2.1.1.1 GovOps and Feature Feedback via Process Models and Wireframes

AVCs' perspectives are pivotal in reviewing conceptual wireframes and the overall logic of GovOps processes. We'll share process maps and wireframes of upcoming features and invite AVCs' insights. Identifying areas of potential confusion and gathering suggestions for enhancement will significantly contribute to our process refinement and quality of work output.

Additionally, to ensure the accuracy of gathered information we're working on setting up an enviroment for regular feedback loops to foster asynchronous cooperation on GovOps process models and feature wireframes.

##### 2.1.1.2 Identification of API Data Points for Document Models

AVCs' expertise is instrumental in identifying key data points crucial for API integration. This ensures efficient information retrieval and informed decision-making, as the specific data elements are purposefully structured to match the objectives and processes of the operational framework. Through their insights, AVCs are in a unique position to help build a streamlined and successful API integration that enhances the MakerDAO ecosystem's operational efficiency.

To optimize API data point identification, we can collaborate with AVCs through organized workshops, tapping into their expertise to highlight crucial data points. By establishing continuous feedback loops, AVCs can consistently refine these selections. Additionally, by creating and testing preliminary API integrations in real-world settings, we can validate their efficiency and effectiveness.

#### 2.1.2 Atlas Accessibility

##### 2.1.2.1 Cooperative Process Mapping and Accessibility

By collectively identifying and streamlining essential processes, this cooperative approach ensures that the Atlas becomes structured and intuitive. Users can then navigate through well-defined workflows and data, making the Atlas easier to understand and interact with, ultimately enhancing its accessibility.

##### 2.1.2.2 Feature Feedback and Accessibility

Through feature feedback, stakeholders contribute their insights to shape the design and functionality of the Atlas. This cooperative input leads to the development of user-centric features and tools that align with the community's needs. In this way, users can interact with familiar and intuitive features, which enhances their overall experience.

Take Ecosystem Actors for example:

MakerDAO stakeholders faced a fragmented and time-consuming process of gathering information about EA’s from various sources like forums and social media.

We made EA’s data accessible and transparent by aggregating their profiles, services, and financial reports onto a single accessible platform.

###### Fig7: Operational Dashboard, a cornerstone of Atlas Accessibility

This approach saved time, enhanced transparency, and empowered stakeholders to make informed decisions based on comprehensive insight, but most of all it made the contens of the Atlas easily accessible to a wider community.

##### 2.1.2.3 Creating Data Structures and Accessibility

The process of creating data structures involves organizing information in a coherent and structured manner. This structured data provides a clear framework for understanding and navigating the Atlas. Cooperative efforts to define and structure data elements ensure that information is presented in a logical and digestible format. As a result, users can more easily locate and comprehend the data they need, contributing to the accessibility of the Atlas.

### 3. Remaining steps

While the steps of Product Design, Business Logic, UI Development, and On-boarding & Release are undoubtedly essential in our workflow, our focus is on standardizing cooperation for the first two steps; we remain open to integrating cooperative practices into these subsequent steps in the future.

**Product Design** segment is centered around creating user-focused solutions, with an emphasis on intuitive document editing and visually compelling dashboards that simplify navigation.

**Business Logic** sets the foundation for the software's core functionality, blending the aesthetics of design with the robustness of operational logic for an optimal user experience.

**UI Development** breathes life into these designs, transforming them into interactive interfaces. This includes the meticulous crafting of editor components and the fusion of diverse data into comprehensive dashboard displays.

**On-boarding and Release** focus on easing user adoption and ensuring an effective software launch. Through guided tutorials and training, users gain proficiency, while promotional campaigns highlight features and ensure the software integrates seamlessly into daily workflows.

### 4.The Role of Powerhouse
As we saw, Powerhouse serves as a vital bridge between these cooperative practices and Atlas accessibility. By implementing a user-friendly interface, Powerhouse acts as a frontend that enables core stakeholders to access the Atlas and interact with its processes. It simplifies the view of Atlas Documents, presenting information in a more organized and manageable manner, making it more accessible to users who interact with it manually.

Additionally, the integration of GAITs further enhances accessibility. GAITs assist users in navigating the Atlas, guiding them through complex processes and data structures. This assistance ensures that even users who are not intimately familiar with the Atlas can effectively engage with it. The combination of Powerhouse's streamlined interface and GAIT support transforms the Atlas into a resource that is more approachable and less daunting for a wider range of users.

In essence, these cooperative efforts, coupled with Powerhouse's user-friendly interface and GAIT assistance, work synergistically to make the Atlas a lot more accessible and less overwhelming. By integrating insights, feedback, and structured data, the Atlas becomes a navigable hub that empowers users to engage effectively and contribute meaningfully to the MakerDAO ecosystem.

### 5. Connect With Us

We thank the Sovereign Finance AVC and Regenerative Finance AVCs for their engaged involvement and valuable contributions and we welcome the community to partake in this cooperative journey, collectively elevating our processes and thus making Atlas more accesbile.

@Powerhouse team