Active case study / Beta
Brick, Mortar & Daughter (BMD)
Skills, learning and procedures can share one operating context once the first product boundary is clear.
Brick, Mortar & Daughter connects skills mapping, workforce planning, learning, onboarding, user data and governance. The current phase is to validate a focused first workflow with an accountable buyer and operating owner before the wider modular direction becomes a repeatable offer.
Organizational work loses traceability when knowledge, people and controls live apart.
The supplied record describes organizations managing training, employee data, procedures, controls, risks and plans across separate documents and applications. The resulting gap is not simply a missing feature: ownership, execution and audit history become difficult to follow.
The public BMD direction needs a focused first product boundary.
The public BMD website presents skills mapping, workforce planning, learning, onboarding, a user data hub, and procedures and governance. Internal records group users, roles, organizational context, content, forms, assignments and activity records as a possible shared core. Procedures, competencies, approvals and organization-specific rules form a configured layer; integrations and implementation work vary by organization.
Participants
A public organizational platform direction connecting skills, learning, people data, procedures and activity records.
System outcomes
Connected modules
- 01Shared core
Users, roles, content, forms, assignments and activity records
- 02Configuration
Procedures, attributes, competencies and approval rules
- 03Implementation
Migration, access rules, integrations and governance
- 01Define a procedure
A process owner turns approved content and rules into an assignable workflow.
- 02Assign and complete work
A role-based participant works through activities, forms or checks.
- 03Review evidence
An accountable owner reviews the resulting activity context.
Feedback loopThe exact workflow, buyer and operating evidence remain to be agreed before this becomes a product claim.
The archive mixes developed capabilities, partial stability, roadmap and ideas.
Earlier development covers learning and content functions, dynamic procedures, user data and some organizational context. The wider roadmap includes people operations, governance, risk, compliance, strategy, performance and AI assistance. None of the roadmap items is presented here as production-ready.
- 01 / LearningCourses, content and activitiesLearning team
Documented or partially stable capability
- 02 / ProcedureDynamic procedureProcess owner
Documented workflow direction
- 03 / OrganizationRoles and competency contextManager
Partly developed organizational view
Scope-decision artifact
Next artifactApproved platform boundary
The next artifact is a canonical identity, capability inventory and first-workflow definition. It is not a broad production-platform claim.
- Canonical name and ownership map
- Current-release capability and defect review
- One buyer and two or three approved workflows
- 01
Foundation hypothesis
One operating layer can connect organizational knowledge and execution.
The archive proposes a shared core with configuration and implementation layers.
Project archive - 02
Public product signal
Brick, Mortar & Daughter publicly names its skills, learning, people-data and procedures direction.
The public website supports this brand and capability direction, but does not resolve the internal portfolio architecture.
brickmortardaughter.com - 03
Scope decision
Use Brick, Mortar & Daughter as the public BMD name while retaining the internal scope boundary.
LMS CO, CoWorks, LMS RS, LMS FR and Co-Trek still require an explicit portfolio and ownership decision before each is represented as part of the same product.
Editorial record - 04
Next evidence
Choose the identity, buyer and first workflows, then review the current release.
The first product decision must separate working capability from defects, roadmap and concepts.
Blocking decisions
Value is conditional on selecting a narrow operational problem.
Organization
- Potentially replace disconnected documents with assigned workflows and visible records.
- Define a repeatable implementation model around a stable core.
Process or learning owner
- Potentially connect content, activity and role context.
- Configure approved procedures without treating every document as a separate system.
Employee
- Potentially work through one role-based environment.
- See assigned work in organizational context.
A buyer and commercial model remain open until the first use case is chosen.
- Primary buyer
- Not selected
The archive names several organizational functions but does not establish one accountable buyer.
open - First application
- Digital procedures, learning or governance workflow
The choice must be made before a product or implementation offer is defined.
planned - Commercial proof
- Not confirmed
No current customer, deployment, pricing or implementation claim is made.
open
- Documented capability set with partial historical implementation evidenceAvailable evidence
- BMD / CoWorks editorial record and supplied archive
- It does not prove a stable release, one buyer, current deployment or full roadmap availability.
The first workflow must prove its value in one accountable organizational setting.
Validation gate
One canonical platform identity and a stable first workflow are approved, reviewed and ready for a named organization.
Gate not yet passedWhat must be true
- openIdentity and ownership
Confirm the name, portfolio architecture and ownership of every included component.
- openRelease review
Separate working capabilities, defects and roadmap items in a current release review.
- to agreeFirst use case
Select one buyer and two or three core workflows.
Validate one workflow before expanding the wider organizational platform.
SKWD carries in
- A documented reusable-foundation hypothesis and partial capability record.
This venture adds
- A controlled validation plan, observable workflow criteria and an implementation boundary.
External proof needed
- An accountable owner, selected buyer and organization willing to validate one workflow.
Next step
Run the first organizational validation.
Bring an accountable buyer, operating owner and one controlled workflow. We will agree the evidence gate, implementation boundary and review cadence before the platform expands.
Brick, Mortar & Daughter is the public BMD brand; the wider internal portfolio boundary is under review.
The public website supports Brick, Mortar & Daughter as the BMD brand and describes its outward capability direction. This record still separates that public direction from internal claims about implementation maturity, shared ownership, integrations, deployment and the wider CoWorks/LMS portfolio.
Brick, Mortar & Daughter is the public BMD brand. Internal records combine implemented, partly stable, planned and conceptual work; shared ownership, scope, deployment and data-governance boundaries for the wider portfolio remain unresolved.