Engagement privacy
People can speak without being exposed.
We listen to individual concerns and use what we learn to improve the work. Leadership receives patterns and recommendations. Private conversations stay private.
The public website
Do not send private records, personal data about other people, credentials, or confidential information through the website inquiry.
Website privacy policyTeam adoption
Listen privately. Report patterns.
Agree what will be collected, who can see it, and how it will be reported before interviews or observation begin.
Participation
Individual conversations are voluntary. We explain the purpose and reporting boundaries before asking people to share concerns.
Private conversations
We learn how people work and where they get stuck. Private interviews are not a channel for attributed complaints to leadership.
Useful reporting
Leadership receives patterns, recurring blockers, and recommendations. Reports omit personal quotes and identifying details, including context that could expose someone in a small team.
Public examples
An improvement can be described anonymously. Publication boundaries are agreed before using engagement information, and private conversations stay private.
Engagement terms
What the written engagement must cover.
Security controls depend on the actual deployment. The scope records owners and verification steps for the selected tools and architecture.
- Scope and source approval
- The work, authorized use, source owner, and approved material.
- Deployment and providers
- The actual environment, system boundary, data locations, responsibilities, and every provider that would process engagement information.
- Access and security
- Roles, permissions, administrative access, authentication, data separation, and verified controls for the selected architecture, including encryption, logging, backup, and network controls.
- Reporting and deletion
- Reporting boundaries, retention periods, deletion requests and verification, offboarding, and any legal or operational exceptions.
- Operational responsibility
- Named contacts, support windows, incident notification and escalation paths, and a safe fallback.
Website inquiries
Start with a short description.
The website privacy policy covers your inquiry. A separate agreement covers information used during an engagement.
Read the website privacy policy- Initial inquiries
- A short description is enough to start. Organization and team size are optional. Keep private records and confidential client information for an agreed engagement.
- Your information
- We use your inquiry to respond and discuss the work. Submitting the form does not subscribe you to promotional email.
- Privacy requests
- You can request access, correction, or deletion of information associated with your inquiry. The website privacy policy explains the process, providers, and retention periods.
Working agreement
Agree the safeguards before work begins.
The written engagement identifies the controls, providers, and support arrangements for the selected environment. Review those records before approving access or sharing engagement information.
People remain responsible for decisions made with AI. We agree how results will be checked and who can act on them.
Engagement privacy questionsStart with a free conversation.
Tell us what's happening and what you'd want to be different. We'll reply to arrange a free introductory conversation. Detailed assessment and implementation are paid engagements, scoped to your needs, onsite or remote.