acooper_initiative/website/governance.html at main · Human-Augment-Analytics/acooper_initiative · GitHub

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
<!DOCTYPE html>
<html lang="en">
<head>
    <meta charset="UTF-8">
    <meta name="viewport" content="width=device-width, initial-scale=1.0">
    <title>Governance & Integration - Real-World Collaboration Initiative</title>
    <link rel="preconnect" href="https://fonts.googleapis.com">
    <link rel="preconnect" href="https://fonts.gstatic.com" crossorigin>
    <link href="https://fonts.googleapis.com/css2?family=Merriweather:wght@400;700&family=Source+Sans+Pro:wght@400;600;700&display=swap" rel="stylesheet">
    <link rel="stylesheet" href="styles.css">
</head>
<body>
    <div class="breadcrumb">
        <a href="https://sites.gatech.edu/human-augmented-analytics-group/">← HAAG</a> <span>/</span> <a href="index.html">Initiative</a> <span>/</span> Governance & Integration
    </div>

    <header>
        <h1>Real-World Collaboration Initiative</h1>
        <div class="tagline">Building a Framework for Academic-Civic Research Partnerships</div>
        <div class="header-divider"></div>
        <div class="header-subtitle">From Charleston Trains to a Replicable Procedure</div>
    </header>

    <nav class="main-nav">
        <div class="nav-container">
           Real-World Collaboration Initiative
            <ul class="nav-menu">
                <li><a href="index.html" class="nav-link">Home</a></li>
                <li><a href="case-study.html" class="nav-link">Charleston Case Study</a></li>
                <li><a href="procedure.html" class="nav-link">The Procedure</a></li>

                <li><a href="opportunities.html" class="nav-link">Opportunities</a></li>
                <li><a href="governance.html" class="nav-link active">Governance & Integration</a></li>
                <li><a href="faq.html" class="nav-link">FAQ</a></li>
                <li><a href="contact.html" class="nav-link">Contact</a></li>
            </ul>
        </div>
    </nav>

    <div class="container-full">
        <main>
            <section id="intro">
                <h2>Governance & Integration</h2>
                <div class="intro-section">
                    <p>This page answers a specific question: <strong>how does the Real-World Collaboration Procedure integrate into HAAG's existing structure, and how is it enforced?</strong></p>
                    <p>The procedure isn't self-enforcing. It requires named roles with clear authority, mandatory checkpoints that gate each phase, a registry to track what's happening across the group, and a reporting cadence that keeps HAAG leadership informed. This page documents all of that — so the procedure has institutional weight, not just good intentions.</p>
                    <p>HAAG operates within Georgia Tech's OMSCS program and provides remote, async students with real research experience. Partnerships are one of the primary mechanisms for that. This governance structure ensures partnerships are run to a consistent standard and that the initiative can continue beyond any single person's involvement.</p>
                </div>
            </section>

            <div class="divider"></div>

            <!-- Decision Authority -->
            <section id="authority">
                <h2>Who Has Authority at Each Phase</h2>

                <p>Each phase of <a href="procedure.html">the procedure</a> has a mandatory Go/No-Go checkpoint. The table below defines who holds authority at each checkpoint and what the outcome must be before moving forward. No phase should be skipped.</p>

                <h3>Partnership Approval Levels</h3>

                <div class="timeline">
                    <div class="timeline-item">
                        <div class="timeline-label"><a href="procedure.html#identification" style="color: inherit;">Phase 1</a></div>
                        <h4>Go/No-Go: Pursue scoping?</h4>
                        <p><em><a href="procedure.html#identification">Identifying Opportunities</a></em></p>
                        <p><strong>Authority:</strong> Faculty advisor + Initiative lead<br>
                        <strong>Outcome:</strong> Approved or deferred</p>
                    </div>
                    <div class="timeline-item">
                        <div class="timeline-label"><a href="procedure.html#scoping" style="color: inherit;">Phase 2</a></div>
                        <h4>Go/No-Go: Scope approved?</h4>
                        <p><em><a href="procedure.html#scoping">Scoping Partnerships</a></em></p>
                        <p><strong>Authority:</strong> Faculty advisor + Initiative lead + Department leadership<br>
                        <strong>Outcome:</strong> Scope signed off or reshaped</p>
                    </div>
                    <div class="timeline-item">
                        <div class="timeline-label"><a href="procedure.html#building" style="color: inherit;">Phase 3</a></div>
                        <h4>Institutional Approval: Agreements finalized?</h4>
                        <p><em><a href="procedure.html#building">Building Relationships & Securing Buy-In</a></em></p>
                        <p><strong>Authority:</strong> Georgia Tech OTT + HAAG leadership + External partner<br>
                        <strong>Outcome:</strong> Formal partnership agreement signed</p>
                    </div>
                    <div class="timeline-item">
                        <div class="timeline-label"><a href="procedure.html#executing" style="color: inherit;">Phase 4+</a></div>
                        <h4>Ongoing Oversight</h4>
                        <p><em><a href="procedure.html#executing">Executing the Partnership</a> / <a href="procedure.html#measuring">Measuring Impact</a></em></p>
                        <p><strong>Authority:</strong> Initiative lead (with faculty advisor)<br>
                        <strong>Decision:</strong> Quarterly: on track? Need course correction?</p>
                    </div>
                </div>

                <h3>Who Approves What</h3>
                <div class="case-study-highlight">
                    <p><strong>Initiative Lead:</strong> Final authority on partnership fit and phase progression. Manages quarterly reviews, ensures procedure is followed, escalates to HAAG faculty leadership as needed.</p>
                    <p style="margin-top: 1rem;"><strong>Faculty Advisor:</strong> Recommends partnership fit, maintains academic standards, manages student team, assesses scope feasibility.</p>
                    <p style="margin-top: 1rem;"><strong>HAAG Leadership:</strong> Reviews partnerships for strategic alignment, approves budget commitments, ensures Georgia Tech policy compliance.</p>
                    <p style="margin-top: 1rem;"><strong>Georgia Tech Office of Technology Transfer:</strong> Reviews IP and licensing agreements, advises on data confidentiality, drafts formal agreements.</p>
                </div>
            </section>

            <div class="divider"></div>

            <!-- Registry & Oversight -->
            <section id="registry">
                <h2>Partnership Registry & Ongoing Oversight</h2>

                <p>Every partnership operating under this procedure must be registered in a HAAG partnership database. The registry is what makes the procedure enforceable at scale — without it, there is no visibility into what's active, what's stalled, or what lessons are being generated.</p>

                <p>Each record should capture: partner organization, faculty advisor, research team lead, start date, research focus, expected duration, current phase, and (at completion) publications, tools delivered, and lessons learned.</p>

                <h3>How oversight works</h3>
                <p>Once a partnership is approved and underway, the research team operates independently for the duration of the semester. The initiative lead does not manage active projects — that's the faculty advisor's role. The initiative lead's job is to maintain the registry and keep the initiative itself healthy.</p>

                <ul class="checkmark-list">
                    <li><strong>Each semester:</strong> Initiative lead reviews all active partnerships, writes a brief summary of outcomes and lessons, updates the website if needed, and decides whether to continue in the role or identify a successor</li>
                    <li><strong>At project completion:</strong> Research team submits a short record to the registry (outputs, lessons, partner feedback) — the initiative lead does not need to be involved in the research itself</li>
                    <li><strong>As needed:</strong> If a partnership runs into a serious issue, the faculty advisor escalates to the initiative lead and HAAG leadership — but this should be the exception, not the norm</li>
                </ul>
            </section>

            <div class="divider"></div>

            <!-- Integration -->
            <section id="integration">
                <h2>How This Fits into HAAG & OMSCS</h2>

                <p>HAAG exists within Georgia Tech's OMSCS program to give remote, async students access to real research experience. External partnerships are one of the primary vehicles for that. This procedure formalizes how those partnerships happen — so research quality is maintained, expectations are clear on both sides, and students are contributing to work that has genuine impact.</p>

                <p>Practically, integration means:</p>
                <ul class="checkmark-list">
                    <li><strong>New faculty and researchers</strong> receive a briefing on this procedure as part of HAAG onboarding. It is the expected starting point for any externally-partnered project.</li>
                    <li><strong>Partnerships carry the HAAG name</strong> only when they have passed a Phase 1 Go/No-Go with HAAG admin sign-off. Once approved, research teams run their own projects.</li>
                    <li><strong>Each semester</strong> the initiative lead reviews the registry, updates the website, and assesses whether the procedure needs updating — keeping the overhead light and the initiative sustainable.</li>
                </ul>
            </section>

            <div class="divider"></div>

            <!-- Continuation & Handoff -->
            <section id="handoff">
                <h2>Continuation & Handoff</h2>

                <p>This initiative was developed as an OMSCS initiative project and is intentionally designed for continuity. The full procedure, partner directory, and case study documentation are ready for a successor to pick up without starting from scratch.</p>

                <h3>Initiative Lead Transition</h3>
                <p>The initiative lead role is reviewed each semester. The current lead decides whether to continue or hand off — this is a natural, low-friction transition built into the rhythm of the initiative rather than a crisis. The incoming lead should be identified and briefed before the semester ends. A clean handoff includes:</p>

                <div class="case-study-highlight">
                    <p><strong>Documentation review:</strong> Walkthrough of the full procedure, governance structure, and partnership registry</p>
                    <p style="margin-top: 1rem;"><strong>Partner introductions:</strong> Warm handover to any active partner contacts, including Charleston and any organizations in active discussion</p>
                    <p style="margin-top: 1rem;"><strong>Communication transfer:</strong> Access to shared folders, email threads, and any ongoing correspondence</p>
                    <p style="margin-top: 1rem;"><strong>Open items briefing:</strong> Status of any active partnerships, pending outreach, or unresolved decisions</p>
                </div>

                <h3>For HAAG Managers Interested in Taking Over</h3>
                <p>If you're a HAAG manager or faculty member interested in continuing or expanding this initiative, reach out to the current initiative lead at <a href="mailto:acooper90@gatech.edu">acooper90@gatech.edu</a>. No prior involvement is required. The documentation is designed to be self-contained, and a structured handoff can be arranged.</p>

                <h3>Procedure Ownership</h3>
                <p>Whoever holds the Initiative Lead role owns the procedure. The core responsibilities are light by design: keep the partner directory reasonably current, write a semester summary, maintain the partnership registry, and be the point of contact for new partnership inquiries. Active projects run themselves — the lead is a steward, not a project manager. The role can be held by a faculty member, a senior researcher, or a designated HAAG manager.</p>
            </section>
        </main>
    </div>

    <footer>
        <p><strong>Last Updated:</strong> April 2026</p>
        <p><strong>Initiative Lead:</strong> Avi Cooper</p>
    </footer>

    <script src="script.js"></script>
</body>
</html>