📦 EqualifyEverything / raci

📄 data.js · 294 lines
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294export const people = [
    { id: 'blake', name: 'Blake' },
    { id: 'gemma', name: 'Jemma' },
    { id: 'stefin', name: 'Stefin' },
    { id: 'trey', name: 'Trey' },
    { id: 'new_support_hire', name: 'New Support Hire' },
    { id: 'amanda', name: 'Amanda' },
    { id: 'chris', name: 'Chris' },
    { id: 'brother_j', name: 'Brother J' },
    { id: 'ck', name: 'CK' },
    { id: 'michelle', name: 'Michelle' },
    { id: 'asya', name: 'Asya' },
    { id: 'jason', name: 'Jason' },
    { id: 'dylan', name: 'Dylan' }
];

export const projects = [
    { id: 'dae', name: 'DAE' },
    { id: 'equalify', name: 'Equalify' },
    { id: 'ai_leaders', name: 'AI Leaders' },
    { id: 'open_source_fund', name: 'Open Source Fund' }
];

export const areas = [
    {
        id: 'dae_team_management',
        label: 'Team Management',
        project: 'dae',
        objective: 'Overarchingly manage the areas in this RACI chart.',
        meetingRegularity: 'Monthly (1st Mondays)',
        informedRegularity: 'On updates',
        effectiveDate: '2026-02-27?',
        r: ['blake'],
        a: ['gemma'],
        c: ['trey', 'chris', 'stefin'],
        i: ['new_support_hire', 'amanda', 'brother_j', 'ck', 'michelle', 'asya', 'dylan']
    },
    {
        id: 'support',
        label: 'Support',
        project: 'equalify',
        objective: 'Provide timely and effective assistance to Equalify users and maintain high satisfaction through comprehensive support services.',
        meetingRegularity: 'Monthly (1st Fridays)',
        informedRegularity: 'On updates',
        effectiveDate: 'TBD',
        r: ['new_support_hire'],
        a: ['amanda'],
        c: ['chris', 'ck', 'trey', 'dylan', 'blake'],
        i: ['gemma']
    },
    {
        id: 'hub_development',
        label: 'Hub',
        project: 'equalify',
        objective: 'Develop, maintain, and innovate the core Equalify Hub platform to serve as the central accessibility management system.',
        meetingRegularity: 'Monthly (2nd Tuesdays)',
        informedRegularity: 'On updates',
        effectiveDate: 'TBD',
        r: ['chris'],
        a: ['blake'],
        c: ['trey', 'amanda', 'ck', 'new_support_hire'],
        i: ['gemma']
    },
    {
        id: 'reflow_development',
        label: 'Reflow',
        project: 'equalify',
        objective: 'Direct the architecture, development, and cross-project integration of the Reflow design system for UI consistency.',
        meetingRegularity: 'Monthly (3rd Wednesdays)',
        informedRegularity: 'On updates',
        effectiveDate: 'TBD',
        r: ['dylan'],
        a: ['blake'],
        c: ['gemma'],
        i: ['chris', 'trey', 'ck', 'amanda', 'new_support_hire']
    },
    {
        id: 'dashboard_development',
        label: 'Dashboard Development',
        project: 'equalify',
        objective: 'Design and implement interactive, data-driven dashboards for visualizing complex accessibility metrics and trends.',
        meetingRegularity: 'Monthly (1st Thursdays)',
        informedRegularity: 'On updates',
        effectiveDate: 'TBD',
        r: ['trey'],
        a: ['blake'],
        c: ['chris'],
        i: ['ck', 'new_support_hire', 'gemma', 'amanda']
    },
    {
        id: 'equalify_wp_plugin',
        label: 'Dashboard WP Plugin',
        project: 'equalify',
        objective: 'Maintain and update the Equalify Dashboard WordPress Plugin.',
        meetingRegularity: 'Monthly (1st Thursdays)',
        informedRegularity: 'On updates',
        effectiveDate: 'TBD',
        r: ['trey'],
        a: ['blake'],
        c: ['chris'],
        i: ['ck', 'new_support_hire', 'gemma', 'amanda']
    },
    {
        id: 'accessibility',
        label: 'Accessibility',
        project: 'equalify',
        objective: 'Enforce and validate rigorous accessibility standards across all Equalify products to ensure an inclusive user experience.',
        meetingRegularity: 'Monthly (1st Tuesdays)',
        informedRegularity: 'On updates',
        effectiveDate: 'TBD',
        r: ['ck'],
        a: ['chris'],
        c: ['brother_j', 'trey'],
        i: ['blake', 'gemma']
    },
    {
        id: 'equalify_release',
        label: 'Release',
        project: 'equalify',
        objective: 'Manage the full lifecycle of software releases, ensuring stability, performance, and seamless deployment of new features.',
        meetingRegularity: 'Monthly (3rd Thursdays)',
        informedRegularity: 'On updates',
        effectiveDate: 'TBD',
        r: ['amanda'],
        a: ['trey'],
        c: ['blake', 'chris', 'ck', 'new_support_hire'],
        i: ['gemma']
    },
    {
        id: 'user_testing_extension',
        label: 'User Testing Extension',
        project: 'equalify',
        objective: 'Develop and maintain specialized tools for gathering and analyzing direct user feedback on accessibility barriers.',
        meetingRegularity: 'Monthly (2nd Fridays)',
        informedRegularity: 'On updates',
        effectiveDate: 'TBD',
        r: ['ck'],
        a: ['chris'],
        c: ['brother_j', 'trey'],
        i: ['blake', 'gemma', 'amanda', 'new_support_hire']
    },
    {
        id: 'operations',
        label: 'Operations',
        project: 'open_source_fund',
        objective: 'Streamline administrative workflows, internal communications, and operational efficiency for the Open Source Fund.',
        meetingRegularity: 'Monthly (3rd Tuesday)',
        informedRegularity: 'On updates',
        effectiveDate: 'TBD',
        r: ['michelle'],
        a: ['blake'],
        c: ['stefin'],
        i: ['gemma']
    },
    {
        id: 'board_creation',
        label: 'Management',
        project: 'open_source_fund',
        objective: 'Oversee strategic governance, stakeholder relations, and high-level fundraising initiatives for the fund.',
        meetingRegularity: 'Monthly (2nd Wednesdays)',
        informedRegularity: 'On updates',
        effectiveDate: 'TBD',
        r: ['blake'],
        a: ['jason'],
        c: ['stefin', 'gemma'],
        i: ['michelle']
    },
    {
        id: 'admissions',
        label: 'Student Services',
        project: 'ai_leaders',
        objective: 'Execute targeted recruitment, streamline the enrollment process, and provide comprehensive support to students throughout the AI Leaders program.',
        meetingRegularity: 'Monthly (1st Wednesdays)',
        informedRegularity: 'On updates',
        effectiveDate: 'TBD',
        r: ['asya'],
        a: ['stefin'],
        c: ['blake'],
        i: ['gemma', 'jason']
    },
    {
        id: 'ail_management',
        label: 'Management',
        project: 'ai_leaders',
        objective: 'Provide strategic direction and administrative oversight for the AI Leaders program and its constituent representation.',
        meetingRegularity: 'Monthly (2nd Thursdays)',
        informedRegularity: 'On updates',
        effectiveDate: '2026-02-27',
        r: ['stefin'],
        a: ['blake'],
        c: ['gemma', 'asya'],
        i: ['jason']
    },
    {
        id: 'ail_platform_buildout',
        label: 'Platform Buildout',
        project: 'ai_leaders',
        objective: 'Execute the initial platform buildout and support until May 14, followed by a transition to a newly established engineering team.',
        meetingRegularity: 'Weekly (Tuesdays)',
        informedRegularity: 'On updates',
        effectiveDate: '2026-02-27',
        r: ['blake'],
        a: ['stefin'],
        c: ['asya'],
        i: ['jason', 'gemma']
    }
];

export const roleDefinitions = {
    R: {
        title: 'Responsible',
        description: 'The person who performs the work or completes the task.',
        color: '#d50032'
    },
    A: {
        title: 'Accountable',
        description: 'The person who is ultimately answerable for the correct and thorough completion of the task.',
        color: '#f59e0b'
    },
    C: {
        title: 'Consulted',
        description: 'Those whose opinions are sought, typically subject-matter experts.',
        color: '#3b82f6'
    },
    I: {
        title: 'Informed',
        description: 'Those who are kept up-to-date on progress or completion.',
        color: '#6b7280'
    }
};

export const sops = [
    {
        id: 'sop_dae_management',
        title: 'Procedure and Management',
        project: 'dae',
        area: 'dae_team_management',
        responsible: 'blake',
        accountable: 'gemma',
        effectiveDate: '2026-02-27?',
        reviewCadence: 'Monthly (1st Mondays)',
        reportRegularity: 'On Updates',
        content: `
<h3>1) Overview</h3>
<p>This SOP overarchingly details how to manage the areas in this RACI chart. <mark><strong>The SOP's primary focus is to empower individual ownership and streamline communication to maximize the performance of team projects.</strong></mark> Each responsible party can create an SOP with those accountable for their RACI area. SOPs are agreements laying out clear objectives and communication strategies that the Responsible and Accountable parties agree to.</p>
<h3>2) Communication Procedures</h3>
<ol>
    <li>Responsible and Accountable parties <strong>collaborate continuously</strong> on the development of the area.</li>
    <li>Those accountable <strong>support</strong> the presentation and <strong>validate</strong> area progress.</li>
    <li>The Responsible person <strong>presents</strong> updates and <strong>solicits</strong> feedback from those who need to be consulted during the regular update meeting.</li>
    <li>Those informed <strong>receive update reports</strong> from the responsible person within the agreed regularity, stipulated in the SOP.</li>
</ol>
<h3>3) Success and Failure Verification</h3>
<p><strong>Success:</strong> Team operations remain strictly within the communication procedures outlined in this document.</p>
<p><strong>Failure:</strong> Procedures are circumnavigated, leading to operational inefficiency.</p>
<p><strong>Failure Examples:</strong> Additional meetings or communication required by parties who are neither Responsible nor Accountable for the specific area.</p>
<h3>4) Remediation</h3>
<p>In the event of failure, the team is expected to work down this sequential list:</p>
<ol>
    <li>Address the system that created the bug causing the failure.</li>
    <li>Increase consultation meeting regularity for the impacted area.</li>
    <li>Update RACI items to ensure clarity and alignment with operational needs. Updating the RACI is the final end of the remediation process and should be prevented at all costs.</li>
</ol>
<h3>5) Procedure Flow Diagram</h3>
<pre class="mermaid">
graph TD
    Start((Operational Start)) --> Process[Continuous Collaboration<br/>R & A Parties]
    Process --> Prep[Accountable Support &<br/>Validate Progress]
    Prep --> Presentation[Responsible Presents & Solicits<br/>Consulted Feedback at Meeting]
    Presentation --> Informed[Informed Receive Regular Update Reports]
    Informed --> SuccessCheck{Procedures Followed?}
    
    SuccessCheck -- Yes --> Success([Success: Efficient Operations])
    SuccessCheck -- No --> Failure([Failure: Procedures Circumnavigated])
    
    Failure --> Remediation1[1. Address System Bug<br/>Causing Failure]
    Remediation1 --> Remediation2[2. Increase Consultation<br/>Meeting Regularity]
    Remediation2 --> Remediation3[3. Update RACI Items<br/>Final End - Prevent if possible]
    
    Success --> Start
    Remediation3 --> Start
</pre>
<h3>6) RACI Update Process</h3>
<p>In the case of a new area implementation or a required RACI update, the following process is followed:</p>
<ol>
    <li><strong>Call a meeting</strong> with those who may be affected by the RACI update and anyone who raised concerns leading to the update.</li>
    <li><strong>Agree on updates</strong> collaboratively during the meeting.</li>
    <li><strong>Note the effective date</strong> on the updated RACI item.</li>
    <li><strong>Proceed</strong> with team operations under the new assignments.</li>
</ol>
        `
    }
];