The review queue was our real bottleneck.Maya Patel · Business Technology
We measured review effort and rework alongside delivery speed.
From question to outcome.
Explore with contextualised AI. Connect with people whose experience fits. Take the next step together and build evidence of what you achieve.
Core membership is free. Explore the illustrative demo without registering.
Think and consider
← Back to the overview
00 · Your context
Set the context that shapes your work.
Your saved role, organisation, sector and subsector inform every answer, so you do not have to explain the basics each time.
- Role
- CIO
- Organisation
- Major UK retailer
- Sector
- Retail & Consumer
- Subsector
- Multichannel retail
At Professional and Organisation levels, you can change these settings to explore a different role, sector or scenario.
← Back to the overview
01 · Bring your challenge
Start with what you need.
Start with a question or create a project space. Explore on your own, or invite your team to share context and work through the challenge with AI.
Your project can stay within your team. Bring in outside expertise when it helps.
Example project · AI development pilotMatt + his team
Matt invites his engineering and security leads to explore together.
“I’m considering introducing AI across my IT team. Where should I start, and what should I be thinking about?”
Quick answer
Second-model check
Deeper research
Quick answerA starting point to refine through conversation.
Second-model checkQuestion assumptions and spot gaps.
Deeper researchUse multiple models and supporting sources.
← Back to the overview
02 · Explore with AI
Go as deep as the question needs.
Explore alone or with your invited team. Bring different perspectives to each answer, sharpen the question and test assumptions. The project keeps your shared context and conversations together as your thinking develops.
Ask→Answer→Refine↻
doshin
“Treat this as an engineering operating-model change, not a licence rollout.”
Matt
What would a sensible first pilot look like, and how would I keep it safe?
Security lead
Let’s agree what data the teams can use before choosing the pilot.
The answer becomes the context for the next question. Continue ↻
← Back to the overview
03 · Connect
Useful connections, as your thinking develops.
As you explore, doshin suggests relevant people, insights, communities and research. Continue with your own team, or bring in a peer or specialist when another perspective would help.
You choose who sees what. Personal conversations stay private. Share project context with invited members, and choose what to share with anyone outside.
Alongside your answer
People, insights, communities and research relevant to your question appear here.
People with experience that fits
Select a person to see their experience, evidence and availability.
Experience shared across the network
What belongs in a safe AI pilot?Sam Taylor · People and Change
Start with one low-risk service and agree the checks before introducing the tools.
Communities connected to this question
Business TechnologyAI adoption, engineering quality and security.
PrimaryPeople and ChangeSkills, confidence and changes to ways of working.
RelatedSources worth examining
NIST AI Risk Management FrameworkGovernance framework · Primary source
UK Government AI PlaybookAdoption guidance · Primary source
Already using your own AI? A planned doshin plugin will help you find relevant people and experience from within that conversation.
Act, if you take it further
← Back to the overview
04 · Agree and engage
Turn a useful connection into the right arrangement.
If a conversation is enough, stop there. If you decide to work together, bring in one person or assemble a team, then agree the scope, responsibilities and route that fit.
You remain in control.
Nothing becomes paid work until the people involved agree what will happen and on what terms.
Choose the route that fits
Open an option to compare responsibilities and fees.
Engage directlyYou and the professional handle the agreement and the work.No doshin charge
- Responsibilities
- Client and professional agree contracts, scope, rates and payment terms, and manage the work together.
- Fees
- No placement fee and no markup: the cost of the work is agreed directly between you. Included with membership.
Use your existing supplierKeep your existing agency or preferred supplier.Your partner’s usual rateNo additional doshin charge
- Responsibilities
- Your supplier confirms contracting and payment with your organisation and the professional. You agree who manages delivery.
- Fees
- You pay your partner’s usual rate. Your supplier pays doshin an administration fee of no more than 5% from its existing margin, with no additional doshin charge to you.
Choose a contracting partnerChoose a partner to handle contracts, timesheets and payments.5% administration fee
- Responsibilities
- You choose from a small selection of contracting partners, based on their services, terms and fees. Your chosen partner handles the agreed contracts, timesheets and payments. Day-to-day delivery stays with you and the professional unless separately agreed.
- Fees
- 5% added to the agreed rate for the administration service; a £500 day rate becomes £525. Shown in full before you commit, whether the professional came through doshin or with you.
Choose a consulting partnerChoose a consulting partner to manage delivery against agreed outcomes.Your partner’s agreed feeNo additional doshin charge
- Responsibilities
- You agree scope, outcomes and responsibilities with your chosen delivery partner, who manages the work and reports progress against those outcomes.
- Fees
- You pay the fee agreed with your consulting partner. The partner pays doshin’s 5% administration fee from its own margin, with no additional doshin charge to you. Scope, responsibilities and the total price are agreed before work starts.
Engage the right support
Take your project into delivery.
Build on the context and conversations already in your project. Confirm the team, responsibilities and outcomes, and invite any agreed specialists or partners into the work.
SHARED PROJECTAI development pilot
ActiveBriefTeamDecisionsOutcomes
Microsoft Teams · Planned integration Continue collaborating in the tools your team already uses.
← Back to the overview
05 · Deliver
Monitor the work.
The shared project keeps the client, the people doing the work and any delivery partner aligned. Keep sight of progress, decisions and agreed outcomes as the work develops.
SHARED PROJECTAI development pilot
In delivery- Work now
- Design a controlled pilot with two engineering teams
- Decision
- Data handling and review checks agreed
- Progress
- Pilot plan ready for sponsor review
- Next
- Begin with Team A and review after four weeks
doshinAPI ↔delivery partner
With permission, secure APIs can exchange agreed progress and outcome updates.
← Back to the overview
06 · Measure the benefit
Turn good work into evidence.
Compare what happened with what success meant at the start. Confirm the outcome and contributions, then agree what belongs on each professional record.
The work informs what comes next. Your next connection can draw on what you have actually done and learned.
Confirm the benefit
Matt and the team compare delivery speed, review effort and rework with the starting point.
Recognise contributions
The team and any specialist confirm their contributions, the results and what they learned.
Update the record
Each person reviews their evidence and agrees what can be shared on their professional record.
What about confidential work, partners or disputed feedback?
Confidential work can still count. Share an agreed confirmation of your role and contribution without publishing sensitive client information. Evidence and publication are separate decisions.
Partners are part of the same process. Placements through agencies or partners report outcomes back so that work can support the professional's record. Clients, professionals and partners can all contribute attributed feedback.
You can respond. Review findings, add evidence or context and question the reasoning before it is recorded. Factual errors are corrected; reviewers remain responsible for the judgement they sign. Feedback is attached to the work and its source, rather than reduced to an anonymous star rating.
Practical questions
Clarity before you commit.
Who owns the work?
Sharing work on doshin does not transfer ownership to doshin. For commissioned work, agree ownership and rights to the deliverables between the parties before the engagement starts.
Can we use an NDA?
Yes. Agree a suitable NDA, confirm that an existing agreement covers the work, or use your own. Make clear who it covers, including any partner, before sharing sensitive information.
Is a suggested person available to help?
An introduction starts a conversation. Availability, interest and acceptance need to be confirmed by both sides; a suggestion is not a booking.
Does anything become public automatically?
No. Your questions and conversations remain private unless you choose to share them. You choose who can see your professional record. For an engagement, the parties review outcomes and agree what evidence can be shared.
Can we use people or suppliers we already know?
Yes. Bring people you already know, contract directly or use your existing supplier. Agree the relevant terms and any optional service fees before starting. See the existing-supplier route.
Start with something that matters to you.
Watch the demo, or register your interest to join as membership opens.