How a Houston Early Education Nonprofit Made Its Knowledge Easier to Use

Organization Overview

A Houston-based nonprofit with 30 employees developed and distributed early education learning tools for teachers, childcare providers, families, and community organizations.

Its team included curriculum specialists, program staff, trainers, outreach employees, development staff, operations personnel, and leadership.

As the organization expanded its programs and partnerships, important information became harder to manage. Curriculum guidance, training materials, grant requirements, partner instructions, program procedures, and internal policies were spread across emails, shared folders, PDFs, presentations, and individual employee knowledge.

The Challenge

The nonprofit had created a large amount of valuable educational content, but employees struggled to find the right version when they needed it.

Program staff frequently asked curriculum specialists to clarify how learning tools should be used.

Training employees searched through old presentations and handouts before workshops.

Outreach staff needed accurate answers about program eligibility, partner requirements, available materials, and delivery procedures.

Grant and development employees relied on program teams for current descriptions, outcomes, and approved language.

New employees had to learn not only their own role, but also how programs, training, partnerships, and reporting requirements fit together.

The organization had strong knowledge, but it was fragmented across departments and dependent on a few experienced employees.

What Was at Risk

When information was difficult to find, employees lost time and partners sometimes received inconsistent guidance.

Using outdated curriculum materials could affect training quality. Inconsistent program descriptions could create problems in grant applications, partner communication, and public outreach.

The organization was also vulnerable when experienced employees left. Important decisions, procedures, and program history were often stored in memory rather than in a shared system.

Leadership needed a way to preserve that knowledge while making approved information easier for the entire team to access.

The Pixeldust Solution

Pixeldust began by interviewing leadership and representatives from curriculum development, training, programs, outreach, fundraising, and operations.

The discovery process identified the questions employees asked repeatedly, the documents used most often, and the procedures that existed only through informal knowledge.

Existing information was collected from SharePoint, email, PDFs, curriculum guides, presentations, grant documents, training manuals, spreadsheets, and internal notes.

Pixeldust then organized the content into a secure SharePoint knowledge hub covering:

• Curriculum and learning tool guidance
• Program descriptions and eligibility
• Training materials and facilitator instructions
• Partner onboarding procedures
• Resource distribution processes
• Grant and reporting information
• Approved organizational language
• Community outreach materials
• Internal policies and procedures
• Employee onboarding resources

Duplicate content was consolidated, outdated materials were flagged, and missing procedures were documented with subject-matter experts.

Permissions were configured so employees could access the information required for their roles while sensitive grant, personnel, and leadership documents remained restricted.

Maisy was then connected to the approved SharePoint content and made available through Microsoft Teams.

How Maisy Was Used

A program employee could ask:

“Which learning tools are approved for this age group?”

A trainer could ask:

“Where is the current facilitator guide for the parent workshop?”

An outreach employee could ask:

“What information does a childcare partner need before joining the program?”

A development employee could ask:

“What is the approved description of this program for a grant application?”

A new employee could ask:

“Who approves changes to curriculum materials?”

Maisy returned answers from approved internal information and directed employees to the supporting documents when more detail was needed.

When information was missing or outdated, Maisy identified the gap instead of producing an unsupported answer.

Implementation

The project began with an assessment of the nonprofit’s programs, departments, information systems, and recurring knowledge problems.

Pixeldust collected existing documents and interviewed employees responsible for curriculum, training, partnerships, reporting, fundraising, and operations.

The content was reorganized in SharePoint using clear categories, document ownership, permissions, approval status, and review dates.

Undocumented knowledge was captured, including partner onboarding steps, curriculum approval processes, training preparation procedures, and reporting responsibilities.

Maisy was configured to retrieve information only from approved knowledge hub content.

The system was tested using real questions from program employees, trainers, outreach staff, development staff, and leadership.

Employees were then trained to access Maisy through Microsoft Teams and to maintain SharePoint as the central source for current organizational knowledge.

Results

Employees spent less time searching through folders, emails, and old documents.

Program and outreach staff provided more consistent answers to partners and families.

Training employees prepared workshops more quickly because current materials were easier to locate.

Development staff gained faster access to approved program descriptions and reporting information.

New employees learned the organization’s programs and procedures without depending entirely on live explanations from senior staff.

Leadership also gained a clearer view of outdated materials and missing procedures that required attention.

Before and After

Before Maisy, employees searched through emails, shared folders, presentations, and personal notes.

After Maisy, they could ask a question in Microsoft Teams and receive an answer based on approved organizational information.

Before Maisy, curriculum specialists and program leaders repeatedly answered the same questions.

After Maisy, their documented knowledge was available across the organization.

Before Maisy, departments sometimes worked from different versions of training and program materials.

After Maisy, employees used the same reviewed source documents.

Before Maisy, important knowledge could leave when experienced employees moved on.

After Maisy, that knowledge remained organized and accessible to the nonprofit.

Key Takeaway

The nonprofit did not need to replace the tools its employees already used.

It needed to organize its educational content, preserve institutional knowledge, and make reliable answers easier to find.

By combining a structured SharePoint knowledge hub with Maisy inside Microsoft Teams, the organization improved consistency, strengthened onboarding, reduced repeated questions, and gave its 30-person team more time to focus on educators, families, and children.