Selected examples of identifying organizational challenges, designing practical solutions, and supporting implementation and adoption.
An applied organizational assessment and improvement initiative — originating as a graduate practicum and continuing beyond the formal practicum period. The assessment surfaced operational friction, knowledge gaps, and workforce sustainability concerns in a service-delivery organization, resulting in a phased improvement plan, six implementation supports, and ongoing implementation planning support.
This initiative originated as a graduate practicum in I/O psychology and organizational effectiveness. I identified several organizational improvement opportunities and proposed them as potential practicum projects. Leadership selected this assessment, and I designed and conducted the work from assessment planning through final recommendations and implementation materials. The formal practicum concluded in May 2026, after which I continued developing implementation resources, refining governance and adoption materials, and supporting implementation planning discussions as the work moved forward.
Several organizational patterns — operational friction, fragmented knowledge systems, and workforce sustainability concerns — had not yet been systematically assessed or documented when this project began.
This initiative originated as a graduate practicum in I/O psychology and organizational effectiveness, and continued beyond the formal practicum period. I had organizational access and leadership support throughout, but not implementation authority.
Implementation decisions rested with organizational leadership. Some recommendations are under consideration or in early planning stages as of this writing. Following the formal practicum period, I continued developing implementation resources, refining governance and adoption materials, and supporting implementation planning discussions — work that is ongoing as recommendations move forward.
These themes emerged consistently across multiple data sources — surveys, interviews, and document review. They are observations, not diagnoses. Each pointed toward a specific type of organizational improvement.
Multi-step workflows and technology friction consumed significant time that could have gone toward service delivery. Staff described this consistently as a design problem — too many steps, not enough value — rather than a workload or staffing problem.
Technology friction: among the highest-rated stressors in survey dataDeparture consideration was meaningfully elevated across the organization — most visibly among staff in the highest-workload roles. Survey patterns suggested structural contributors more than individual factors.
Majority of frontline staff indicating meaningful departure considerationProcedures were inconsistently documented. Institutional knowledge transferred through relationships more than systems. This created fragility — particularly if experienced staff left — without a consistent mechanism for preserving that knowledge.
No centralized resource system; informal transfer as the primary mechanismStaff described decisions communicated without context, limited visibility into follow-through, and uncertainty during transitions. The pattern pointed to a structural gap — no consistent communication channel or norm for sharing rationale — not to bad intent.
Transparency concerns surfaced across the majority of interviewsFrontline roles carried complex, judgment-intensive decisions, often without formal guidance or consistent documented norms. Staff managed this largely informally through peer consultation, which worked — but wasn't sustainable or equitable across teams.
Decision burden among the most frequently cited themes in interviewsPeer support was the highest-rated dimension in the survey by a clear margin, and low in variance — this wasn't a few people feeling supported, it was nearly everyone. The recommendations tried to build on it more deliberately, rather than leaving it entirely informal.
Peer support: near-ceiling in survey data, consistently cited in interviewsI chose a multi-method approach so findings from one source could be checked against others before drawing conclusions. All data collection was conducted by me, with appropriate consent and confidentiality procedures for a graduate practicum.
Custom instrument built on established frameworks from the organizational psychology literature — covering workforce experience, workload strain, support structures, and intent to stay. Administered to the full staff group; analyzed in SPSS.
Semi-structured interviews conducted with staff across role levels. Transcripts coded inductively using structured thematic analysis to identify recurring patterns and check them against survey findings.
An exploratory focus group was conducted early in the project to better understand staff experiences and surface emerging themes. Findings from that session informed the design of the survey and interview guides. Focus groups also helped surface cross-team dynamics and workflow friction that individual methods would have missed.
Descriptive statistics, scale reliability analysis, and correlation analysis in SPSS. Correlations were used to identify which factors tracked most closely with retention concern — to inform prioritization, not to establish causation.
Review of operational documentation, communication artifacts, and available process materials to identify gaps not surfaced through self-report alone.
I treated findings as credible only when they appeared in more than one data source. This kept conclusions grounded and helped distinguish organizational patterns from individual perspectives.
These findings shaped the recommendations. Each is supported by more than one data source — not conclusions drawn from a single question or interview.
Survey data showed a notably strong association between organizational strain and disengagement — stronger than the relationship between raw workload volume and disengagement. Interview data supported this: staff weren't describing being overwhelmed by the work itself. They were describing friction around it — technology that slowed them down, process steps that created more overhead than value. This suggested workflow redesign was worth prioritizing alongside — or ahead of — staffing considerations.
The highest-workload role group showed the most elevated departure consideration — meaningfully above the pattern for other staff groups. But departure consideration was also widespread organization-wide. I reviewed published workforce research on similar roles for additional context, which helped frame this as a structural concern worth addressing rather than a problem isolated to one team.
Procedures were inconsistently documented across teams. Onboarding happened informally. New staff learned primarily through peer relationships rather than documented processes. Document review confirmed the gaps — there wasn't a centralized, reliable place for staff to find operational guidance. The practical risk: losing experienced staff meant losing knowledge that hadn't been captured anywhere else.
This came up across the majority of interviews, across tenures and role types. Staff described decisions that arrived without much context, concerns raised but not visibly followed up on, and uncertainty that lasted longer than it needed to. Organizational research on procedural fairness suggests that brief rationale-sharing — "we changed this because X" — meaningfully reduces the sense of arbitrariness, and doesn't require large communication investments. The gap looked structural: no consistent channel, no norm for sharing context.
Peer support scored at the top of the survey by a clear margin, with low variation across respondents. Staff also consistently cited peer relationships in interviews as what made the job manageable. This wasn't just a morale finding — it pointed to a real organizational asset. The recommendations tried to build on it more deliberately: formalizing peer consultation so it didn't depend on individual relationships or informal access, and connecting it to knowledge-sharing and cross-team work.
Several staff members brought up work flexibility on their own during interviews — without being prompted. They described it as something that helped them manage the demands of the role. When people spontaneously mention a working condition as something that helps them sustain their performance, it's a signal worth treating as a meaningful protective factor — not just a scheduling preference.
Recommendations were organized into six areas, each linked to a specific finding. They were designed to be implemented gradually — prioritizing lower-lift changes first, building toward more structural ones over time.
These artifacts were developed as part of the practicum and refined afterward — each one addressing a specific finding and designed to minimize the additional work needed to put it into practice. Status reflects where things stood at the time of the initial presentation.
Repetitive stakeholder correspondence was consuming time identified as displacing higher-value work. This library of structured templates for the most common communication types reduces drafting burden, improves consistency, and frees staff capacity for work that requires individual attention.
Procedures were underdocumented and institutional knowledge lived in individuals rather than systems. This framework — with an index structure, named custodian roles, and an update protocol — gives staff a reliable place to find operational guidance and reduces the organization's dependence on individual memory.
No consistent mechanism existed for leadership communication or for tracking procedural changes. This two-part artifact — a recurring update template and a change log — creates a regular communication rhythm and gives staff visibility into what decisions have been made and why.
High-volume correspondence was identified as a significant contributor to operational friction. This framework supports responsible evaluation of AI-assisted drafting — covering governance policy, usage guidelines, a staff adoption guide, and a quality review protocol. Governance is treated as a prerequisite, with leadership approval required before any adoption.
A diagnostic assessment captures a snapshot — without a follow-up mechanism, there's no way to know whether conditions improve. This shorter, recurring survey tracks the same key indicators as the baseline (workload, support, retention intention) so leadership can compare results over time and identify concerns before they worsen.
Staff made judgment-intensive decisions without documented norms, creating inconsistency across teams and added cognitive burden. This reference captures common decision types with guidance on how they've been handled, clarifying questions, and escalation paths — a shared resource that supports consistent practice rather than informal precedent.
The roadmap I presented to leadership — sequenced to prioritize lower-effort changes first, with more structural work following as readiness develops. Implementation decisions rest with organizational leadership.
The main adoption risk I saw was initiative overload — introducing too much change at once to a workforce that was already stretched. The phased approach tries to avoid this: Phase 1 items were chosen because they feel like relief, not more work. If the first changes feel burdensome, the rest won't get traction.
I also tried to design each artifact with a named owner — not just an approving leader, but someone responsible for maintaining it over time. That's usually where implementation stalls: something gets created, presented well, and then slowly forgotten because no one is accountable for keeping it current.
The AI governance framework was included because the operational analysis pointed to high-volume, time-consuming correspondence as a significant source of friction — and AI-assisted drafting could meaningfully reduce that friction in the right context.
But the work context involves sensitive information, which changes the risk calculus. So rather than recommending a specific tool, I built a governance-first structure: what information is appropriate to include, how to review AI output before using it, and the requirement that leadership formally approve any adoption before it happens. The artifact is a framework for responsible adoption — not a technology recommendation.
Survey and interview data used to identify where to focus recommendations. All figures generalized for portfolio presentation — specific numbers and group sizes are not shown. Patterns are representative of actual findings.
| Survey Relationship | Association | How I Used This |
|---|---|---|
| Organizational strain → Disengagement | Very strong positive | Suggested workflow and process friction were more central to disengagement than workload volume alone — supported prioritizing workflow simplification |
| Disengagement → Intent to leave | Strong positive | Grounded the case for treating disengagement as a retention concern, not just a morale issue |
| Workload strain → Organizational strain | Strong positive | Connected workload pressure to downstream disengagement and departure patterns |
| Peer support → Lower intent to leave | Meaningful negative | Supported designing peer cohesion as a structural asset — formalizing it rather than leaving it informal |
Job Demands-Resources (JD-R) framework — This shaped how I built the survey and interpreted the data. The core idea is that workforce strain tends to emerge when ongoing demands (workload, administrative burden, emotional labor) outpace available resources (peer support, autonomy, effective tools, recognition). The pattern I found fit this reasonably well — demands were elevated across multiple dimensions while key resources, particularly operational tooling and leadership visibility, were more limited. Recommendations tried to address both sides.
Procedural fairness research — The communication recommendations draw on a fairly consistent finding in organizational psychology: people's experience of fairness is shaped significantly by whether they understand the reasoning behind decisions, not just whether they agree with the decisions themselves. Brief rationale-sharing tends to reduce perceived arbitrariness over time, and doesn't require large communication infrastructure. That's why the change log and leadership update template are simple, low-effort artifacts — the goal was to make this behavior easy, not comprehensive.
A note on the SPSS analysis — I conducted descriptive statistics (means, standard deviations), reliability analysis (Cronbach's alpha for scale consistency), and bivariate correlations. I did not conduct regression analysis or any analysis designed to establish causation. Correlations were used as an interpretive tool to identify which survey dimensions tracked most closely with retention concern, to inform where recommendations should focus. This is a graduate practicum analysis, not a validation study.
The workforce assessment serves as the featured case study because it is the most comprehensive example of this work. The initiatives below demonstrate the same underlying approach across different problem types: identifying an organizational need, designing a practical solution, building the systems to support it, and enabling consistent adoption over time.
The organization lacked a documented, reusable process for chairing hiring searches. Each search depended on institutional memory held by individuals, creating inconsistency across committees and significant coordination burden for whoever was leading the effort. New or less experienced search chairs had little to draw on.
I designed and chaired a full hiring search and documented the process into a reusable guide — covering shared workspace setup, applicant review forms, scheduling logic, interview scripts, vote tracking, and candidate communication templates. The guide included formula-based spreadsheet infrastructure to automatically aggregate committee evaluations by applicant. Templates were developed for each stakeholder touchpoint: offer calls, confirmations, itineraries, and rejections.
The initiative transformed search knowledge that had previously lived informally across individuals into a structured, reusable process. Consolidating templates, evaluation tools, communication resources, and procedural guidance into a single reference creates repeatable hiring infrastructure — something future search chairs can build from rather than reconstruct from scratch, and that preserves organizational knowledge beyond the individuals who held it.
All incoming requests — regardless of complexity — were routed through the same appointment-based process. Where documentation already supported a decision, this created unnecessary waits and consumed specialist capacity that should have been available for cases requiring individualized review. Leadership identified this as an operational problem and selected me to pilot a solution.
I owned design and implementation end-to-end: developed eligibility criteria, built a 13-step workflow with system-level record-keeping steps, created email templates and communication protocols, and designed tracking infrastructure. I ran the pilot, refined steps based on observation, then trained staff using a phased rollout and provided ongoing guidance to support consistent use.
The workflow moved from pilot to active use across the team. Students whose documentation already supported a decision could receive accommodations within days rather than waiting weeks for a scheduled appointment. At the same time, specialist capacity was freed for cases that genuinely required individualized review — improving both service responsiveness and organizational resource allocation.
Operational resources — procedures, tracking tools, templates, reference guides, and shared logs — were distributed informally across the organization with no central index. Staff found resources through word of mouth or by asking colleagues, which created inconsistency and made onboarding and cross-unit coordination harder. No system existed for tracking what resources were current, who owned them, or where to find them.
I designed and built a structured, multi-tab resource directory in Google Sheets — organized by functional unit with a consistent column architecture (Resource Name, Category, Purpose, Format, Location, Owner, Notes) and a color-coded category system. Each unit tab was designed for its lead to populate and maintain, with an archive tab for retired resources. The directory indexes new infrastructure from the broader organizational improvement initiative — including the Communication Library and Change Log — in a single attributed location.
The directory was introduced in Spring 2026 and is in active use. It replaced informal peer transfer as the primary mechanism for finding operational resources and established named ownership for each entry.