Implementation in context
Selected work
Real situations, practical decisions and the technical work carried through to a usable result.
IT Mushroom project
Collision Plus
Updating wireless without replacing the whole network
Collision Plus was experiencing unreliable wireless and network behavior. We assessed the existing environment and retained the usable firewall and switches rather than replacing the whole network.
When the original wireless equipment choice became impractical, we adjusted the hardware direction. We installed and configured two managed wireless access points and retired the previous production wireless.
We tested the completed installation and verified the new wireless environment was working as intended.
- RetainedInternet, firewall & switchingExisting network foundation
- ReplacedTwo managed access pointsPrevious production wireless retired
- VerifiedCompleted wireless installationConnectivity and area checks
What we retained and checked
The assessment supported a selective wireless change rather than replacement of the whole network. Existing firewall and switching equipment stayed in place.
After configuring the access points, we checked connectivity and the areas served by the installation. The work replaced the wireless equipment that needed attention while keeping the usable network foundation.
IT Mushroom project
DH Build
Moving business files into company ownership
Important business files were held in person-owned Google Drive storage. We designed a company-owned Google Workspace and Shared Drive structure so the business could keep using and administering its information as people and needs changed.
We mapped the source information into that structure, migrated and organized the files, and performed migration and validation checks. We handed over documentation so the company could continue administering the environment.
- Starting pointPerson-owned storageExisting business files
- DestinationCompany-owned Shared DrivesOrganized around the business
- Handed offAdministration & documentationMigration checked and documented
Mapping, checks and handoff
We mapped source locations to their destinations and used file and folder comparisons, checksums for eligible files and exception tracking to check the migration.
The handoff guide explained the structure and administration of the environment, giving the company a practical reference for managing its business files.
Prior professional work
Building a coaching workflow around an existing LMS
A coaching program used a learning management system (LMS) for its learning content. The team needed intake, coach assignment, access and staff administration to work together.
- IntakeIntake recordsSupporting information
- AssignmentCoach / admin workflowAssignment state and exceptions
- AccessLearning accessExisting platform + supporting logic
Before founding IT Mushroom, Chris served as lead developer for the supporting system. He designed and built portals, database-backed records and workflow logic connecting those steps, retaining and extending the existing LMS.
How assignment, access and administration connected
The supporting system connected coach assignment with learning access and staff visibility. It handled reassignment and other exceptions alongside the normal path from intake to coaching.
The portals and records gave coaches and administrators ways to manage the work around the learning content without replacing the existing LMS.
Your situation
What needs to work better?
Bring us the situation, the change ahead or the work your tools cannot quite handle. You do not need the right service label or a finished technical plan.