Start here
Advisory for unclear AI, security, and service work
Turn unclear work
into decisions,
review points,
and usable material.
Fragment Practice helps teams clarify AI use, security controls, and service concepts into decision material, review logic, responsibility boundaries, and handoff-ready notes.
Useful when the work needs to become easier to discuss, review, explain, hand off, or move into the next phase.
Decision materialReview pointsResponsibility boundariesHandoff material
Independent founder-led advisory practice based in Takamatsu, Japan.
Where this is useful
For work that is moving, but not yet ready to decide or hand off.
Useful when the next step needs clearer criteria, review points, responsibility boundaries, or material other people can use.
Useful when
The work is moving, but the decision basis is weak
There is pressure to move, but the criteria, ownership, review points, or next-step logic are still unclear.
Decision basisOwnershipNext move
Useful when
AI use needs reviewability and responsibility
Use cases, input and output boundaries, human review, approval, responsibility, and business impact need a workable shape.
AI useReviewabilityResponsibility
Useful when
A service concept needs a clearer working shape
A concept has momentum, but assumptions, role split, cost logic, sequencing, or handoff conditions are still too loose.
Service conceptWorking shapeHandoff
What this leaves behind
Practical material for discussion, review, and the next phase.
The work is not only advice. It should leave behind material that helps people decide, explain, review, or carry the issue forward.
What this can leave behind
Decision brief
Issue maps, decision points, options, tradeoffs, and next-step logic for discussion or management review.
Issue mapOptionsNext steps
What this can leave behind
Review and responsibility map
Review points, responsibility boundaries, approval logic, escalation paths, and role expectations.
Review pointsResponsibilityApproval
What this can leave behind
Handoff-ready material
Briefs, review setups, requirement frames, matrices, or roadmap notes that other people can reuse in the next phase.
BriefsReview setupRoadmaps
Main path
Recognize the situation, then choose the support shape.
Cases helps you see whether the situation is close. Services helps you choose how direct support can begin.
Cases
Recognize the situation
Start here when you want to see whether your situation is close to the kinds of issues this practice supports.
RecognitionSituationsFit
Services
Choose the support shape
Use Services to compare a Structuring Session, a Decision & Operating Model Sprint, and Ongoing Advisory.
SessionSprintAdvisory
Products and Writing
Use a lighter layer when direct support is not yet the next move.
Products are for reusable working kits. Writing is for public thinking and language that may help before a product, service, or inquiry.
Products
Start with a reusable kit
Use Products when a self-guided kit or working material may be enough before direct support is needed.
Reusable kitSelf-guidedSmaller step
Writing
Read the thinking behind the work
Use Writing for essays and notes on AI, judgment, responsibility, work, and the human distance around technology.
EssaysJudgmentHuman distance
Practice boundaries
A small advisory practice for structure-heavy work.
This is not broad implementation coverage. The focus is clearer judgment, review, responsibility, and working material for issues that need to hold in practice.
Practice boundary
Structure-heavy advisory
Best suited to live issues that need clearer criteria, review, ownership, and usable material before more activity is added.
AdvisoryStructureLive issue
Practice boundary
Focused, not always-on
Designed for bounded support, not broad implementation coverage, staff augmentation, or PMO replacement.
BoundedFocusedNot PMO
Next step
Start from the issue, then move toward the right layer.
If the situation feels familiar but still hard to name, start with Cases. If the issue already needs direct support, use Services to compare the session, sprint, and advisory options. If a reusable kit is enough, use Products. If the issue is hard to classify, use Contact.