Create a visual format to express the following: IT and Systems Management Proposal
IT and Systems Management Proposal
Prompt: The organization is currently facing significant inefficiencies due to fragmented and outdated systems. Many of the operational functions, such as project management, communication, resource allocation, and reporting, are relying on a mix of manual processes and disconnected software tools. This is leading to inconsistent workflows, duplication of effort, and difficulty in tracking key performance metrics across teams. As Deputy Director of People and Operations, you are tasked with selecting and implementing a more integrated and efficient system to address these issues.
What steps would you take to evaluate, select, and implement a new system or suite of systems to streamline these operational processes? Consider the following:
How would you assess the existing systems to identify inefficiencies and gaps? What criteria would you use to evaluate potential systems (e.g., scalability, integration, user experience)? How would you ensure that the selected systems align with both short-term operational needs and long-term strategic goals? How would you handle the transition from the old systems to the new ones and ensure minimal disruption to ongoing operations? Key points to consider in the response:
Evaluation of current systems (audit, feedback from staff, pain points). Criteria for selecting new systems (integration capabilities, scalability, ease of use, vendor reputation, cost). Mapping operational workflows to identify key system requirements. Change management strategies for system implementation (training, phased rollout, communication). Addressing potential resistance to change and ensuring buy-in from stakeholders. Monitoring and optimizing systems post-implementation (feedback loops, system upgrades). Creating people-centered, culturally reflective processes and systems that support a liberatory workplace, respect the sanctity of Black labor and leadership, and supports the wellness of both the organization and its people. Please prepare a visual presentation of your work (e.g. a slideshow, a prezi, an info-graphic, flow-chart, mind-map, timeline, or slide deck) and consider audience engagement, learning styles, and accessibility. You may make assumptions about any information not included in these documents in order to support.
As Deputy Director of People and Operations, I’d approach this as a people change just as much as a systems change. The technology matters, but the real success is whether staff feel their work is easier, clearer, and more sustainable after we implement it.
My guiding priorities would be:
- Make people’s day-to-day work simpler, not heavier.
- Increase clarity, transparency, and trust.
- Build something that can grow with us, not something we’ll outgrow in a year or two.
I’d structure the work in four main phases: understand, decide, implement, and improve.
- Understand: Assess the existing systems and pain points
I’d start by listening before prescribing any solution.
- Map what we’re actually using
– Create an inventory of all tools and processes used for:
– Project and task management
– Communication (internal and external)
– Resource allocation (staffing, budgeting, scheduling)
– Reporting and dashboards
– Include both “official” systems and the workarounds people rely on (spreadsheets, group chats, personal docs).
- Listen to staff at all levels
– Hold listening sessions and short interviews with a diverse cross-section of staff: program, operations, leadership, and especially those doing high-volume, detail-heavy work.
– Ask simple, concrete questions:
– Where do things fall through the cracks?
– Where are you copying and pasting the same information into multiple places?
– What tools do you wish you could stop using tomorrow?
– What’s one thing that would make your job feel easier or less stressful?
– Offer anonymous feedback options so people can be honest without worrying about hierarchy.
- Observe the workflow, not just the tools
– Map a few representative workflows end to end (for example: “new project from idea to completion” or “monthly reporting cycle”).
– Identify:
– Manual handoffs
– Duplicate data entry
– Dependencies on one or two “hero” staff who hold all the knowledge in their heads
– Bottlenecks that consistently slow work down
- Use data, but keep it humane
– Where possible, look at:
– Time spent on manual reporting
– Number of tools used to accomplish a single task
– Delays or rework in key processes
– Combine the numbers with people’s lived experience so we don’t reduce staff to metrics.
The outcome of this phase would be a clear, shared picture of:
- Our biggest pain points
- The most critical gaps and inefficiencies
- A prioritized list of problems we are actually trying to solve
- Decide what we need: Define requirements and evaluation criteria
Before looking at vendors, I’d co-create a set of requirements with staff so we’re not chasing shiny features.
- Clarify must-haves vs. nice-to-haves
– Must-haves might include:
– Centralized project tracking with clear ownership and deadlines
– Integrated communication or at least strong integrations with current communication tools
– Resource allocation visibility (who is working on what, and at what capacity)
– Robust but usable reporting and dashboards
– Nice-to-haves might include:
– Built-in time tracking
– Advanced automation
– Additional collaboration features
- People-centered criteria
I’d prioritize:
– Ease of use: Intuitive interface, low learning curve for non-technical staff
– Accessibility: Compliance with accessibility standards; usable with screen readers, good contrast, keyboard navigation
– Language & inclusivity: Support for different language needs and a design that works for different working styles and roles
– Minimizing cognitive load: A system that reduces context-switching and the number of places staff have to check each day
- Technical and organizational criteria
– Scalability: Can the system grow with us in users, data, and complexity?
– Integration: Ability to connect with core tools (email, calendar, file storage, HR/finance where appropriate). Open APIs or standard integrations are a big plus.
– Configurability vs. customization: We want to configure without needing heavy custom development that locks us in.
– Security and privacy: Role-based permissions, data protection, compliance with relevant regulations.
– Total cost of ownership: Licensing, implementation, training, ongoing admin time—not just the sticker price.
– Vendor support and stability: Quality of onboarding, documentation, and support; likelihood they’ll be around and evolving.
I’d translate this into a simple scoring rubric so we can compare options transparently and fairly.
- Evaluate and select: Involve the people who will use it
- Create a short list
– Based on requirements, identify 3–4 systems (or suites of systems) that:
– Cover most of our core needs
– Are known to be strong in collaboration/project management, resource visibility, and reporting
- Run demos and hands-on trials
– Arrange short, focused demos tailored to our real workflows, not generic sales pitches.
– Provide sandbox access for a small cross-functional working group to test:
– Typical day-to-day tasks
– Reporting needs
– Ease of onboarding for new staff
- Center staff voices in the decision
– Form a selection committee with representation from different teams, roles, and identities.
– Use the scoring rubric plus qualitative feedback:
– How did it feel to use this?
– What would be easier with this system?
– What trade-offs are we willing to accept?
- Make a clear, documented choice
– Recommend a primary system (or tightly integrated suite) with:
– Rationale tied back to our original problems
– Risks and mitigation plans
– High-level implementation timeline and resource needs
- Implement with care: Change management and roll-out
This is where many good tools fail—so I’d be very intentional here.
Tell the story of the change
– Communicate early and often:
– Why we’re changing (rooted in what staff told us)
– What will be better for people’s daily work
– What will stay the same
– How staff will be supported through the transition
– Use multiple channels: live meetings, written updates, FAQs, and space for questions.
Pilot before full rollout
– Start with 1–2 teams as a pilot:
– Configure the system to their workflows
– Test data migration and integrations
– Gather real feedback and refine setup
– Adjust training, configuration, and documentation based on what we learn.
Invest in training and support
– Offer:
– Role-based training sessions (managers, project leads, general staff)
– Short “how-to” guides and video snippets for common tasks
– Drop-in office hours or “system clinics”
– Identify and support a network of “power users” or champions in each team to help peers and provide feedback.
- Manage data migration carefully
– Clean and standardize data before moving it.
– Run tests with a subset of data to avoid surprises.
– Where needed, run old and new systems in parallel for a short, defined period to reduce risk
- Measure, learn, and iterate
Finally, I’d treat this as an ongoing practice, not a one-time project.
Define what success looks like
– Examples:
– Reduction in duplicate data entry
– Faster time to generate key reports
– Increased on-time project completion
– Improved staff satisfaction with tools and workflows
Check in regularly
– 30/60/90-day check-ins with teams and leadership.
– Quick pulse surveys to understand how the system is landing.
– A simple feedback channel for staff to suggest improvements or flag issues.
- Establish light governance
– Clarify ownership:
– Who administers the system?
– How are changes requested and approved?
– How do we onboard and offboard users?
– Keep configuration changes aligned with our original goals: simplicity, transparency, and ease of use