Discovery research · no product access
For small, trusted project groups
Important project context gets lost between the tools.
A decision starts in chat, its reasoning stays in somebody’s memory, the task moves to a board, and the file lands in another account. Weeks later, the group can find the outcome—but not why it happened.
Interviews come before any detailed concept showing. Harbour is a working name at a temporary working domain. Nothing here is available for sensitive use.
Monday · group chat
“Let’s keep the existing data model—the migration risk is too high.”4 replies · rationale discussed
The research question
What does fragmentation actually cost a group?
We are studying the moments when people repeat work, reopen settled debates, miss a commitment, or depend on one person to reconstruct the past.
The goal is to understand the workflow before proposing a product. We are looking for recent examples, not reactions to a feature list.
Who should participate
Groups doing real work across conversation and tools.
Most relevant groups have roughly 3–12 active participants and a recurring project where context matters.
Founders and small product groups
Teams carrying product, commercial and delivery decisions across chat, documents and task boards.
Consultants and client project groups
Mixed teams that need to preserve decisions and hand-offs across organisational boundaries.
Engineering, architecture and research collaborations
Groups where technical reasoning matters as much as the final decision.
Open-source maintainers
Distributed collaborators reconstructing history across issues, chat, pull requests and documents.
Committees and private working groups
Small trusted groups that need continuity without adopting a large organisation-wide system.
A 30-minute conversation
We start with one recent project.
The interview is about how work happens today. We will not ask you to disclose confidential project content, client names, credentials, or message history.
- 01
The project and tool chain
Where conversation, files, tasks and decisions moved from start to finish.
- 02
Retrieval and coordination failures
A time somebody could not recover context, repeated work or missed a hand-off.
- 03
Switching and platform constraints
What blocks another application, and which desktop, mobile or browser access is mandatory.
- 04
Trust requirements
What the group would refuse to share, what must be recoverable, and what would make a tool untrustworthy.
A research concept, not an available service
Private spaces that remember.
Harbour is exploring whether conversation and source-linked decisions, tasks, notes and files should live in one shared workspace instead of separate systems.
Recovery and privacy are treated as workflow questions: what survives device loss, what another service can learn, and how a person can return to the evidence behind a summary or decision.
If an early prototype becomes available, it will be clearly labelled and limited to synthetic or low-risk data.
Read the research notesInterview application
Tell us enough to prepare—not the sensitive details.
Applications are not yet open in this repository configuration. You can review the questions now. No information will be sent until the approved endpoint and human-verification configuration are present.
- 30-minute discovery interview
- No request for confidential project content
- Future design-partner interest is optional
- Ordinary website application data, covered by the website privacy notice
Honest status
Research first. Claims later.
This static site recruits interviews. It is not an application, account service or place to store group work.
The public domain harbour-app.org and the name Harbour are temporary working choices, not evidence of final naming or legal clearance.