Fragment Practice helps organizations clarify judgment, responsibility, review, and operating structure when important work is already moving but still too mixed or too weakly structured to carry well.
Fragment Practice LLC is an independent operating design studio based in Takamatsu, Japan, founded and led by Yasuhiro Shinsho.
Good fit
A mandate or initiative already exists, but ownership, review, and sequencing are still too implicit.
One person is carrying too much translation, prioritization, and judgment alone.
Governance, rollout, service design, and execution support are being treated as one problem.
Typical situations
Fragment Practice is most useful when something important is already moving, but the role split, review structure, judgment basis, or next-step design is still too weak to carry the work cleanly.
Typical situation
A mandate, target, or internal push already exists, but ownership, sequencing, review, and operating boundaries are still too unclear to carry the work cleanly.
Typical situation
A sponsor, project owner, or push lead is holding prioritization, explanation, review, and decision support alone because the structure is still too implicit.
Typical situation
Governance, rollout, service design, PMO, education, and execution support are bundled together and need to be separated before the initiative can move well.
Start here
The site stays intentionally small. Services is the direct support layer. Knowledge is the reusable layer. Writing is the public-thinking layer. Contact is the simplest starting point when the issue is real but still hard to classify.
Services
Use Services when the issue is already moving and needs clearer structure, better judgment support, or a more workable operating model.
Knowledge
Use Knowledge when a lighter, reusable structure may be enough before a tailored engagement is necessary.
Writing
Use Writing when the next useful move is sharper language, a clearer frame, or a better way to understand the shape of the issue.
Contact
Use Contact when the work is already moving, but you are still unsure what kind of support, scope, or entry point makes the most sense.
Representative outputs
The point is not the document itself. The point is to turn a live but under-structured issue into something people can judge from, review, and move through.
What this section shows
Short document-like excerpts and structure previews.
What it is not
Not a full sample library and not client material.
What it helps answer
What kind of working document usually remains at the end.
Memo
Example outputUsed when a live initiative has momentum, but the real issue, ownership logic, and basis for judgment are still too unclear.
Typical structure
6 sections
Typical use
When this becomes useful
A sponsor-led push exists, but the work keeps returning to the same person for interpretation and next-step judgment.
Targets or pressure exist, but the initiative still lacks a shared basis for comparison, review, and escalation.
The team does not need more activity first. It needs a clearer structure for deciding what kind of work this actually is.
What remains as the deliverable
Usually remains as a decision-ready memo that reduces repeated reframing and gives the next move a more usable basis.
Setup
Example outputUsed when a service or program concept already exists, but the viability conditions, role split, component requirements, and operating model are still under-structured.
Typical structure
6 sections
Typical use
When this becomes useful
A service idea has formed, but product selection is happening before the service structure itself is clear.
The team needs to evaluate viability, not just features — including role boundaries, cost logic, and delivery assumptions.
Different actors will likely carry different parts of the model, but responsibility and operating split are not yet explicit.
What remains as the deliverable
Usually remains as a structure brief that helps a team compare options before jumping into detailed build-out or vendor choice.
What this changes
The practical gain is a stronger basis for judgment: clearer scope, better review, more usable materials, and less dependence on one person carrying the whole structure alone.
What this changes
The gain is often not doing more. It is separating what has been mixed together so governance, rollout, service design, and execution support can be handled on the right terms.
What this changes
Instead of relying on one person’s interpretation, the work creates a clearer basis for comparison, recommendation, escalation, and review.
What this changes
Usable materials and clearer operating structure reduce restart cost, strengthen continuity, and make the next move easier to carry across people and teams.
Next step
If the issue is already active, start with Services. If the need is lighter or reusable, start with Knowledge. If you want conceptual clarity before deciding how to engage, start with Writing. If the scope is still hard to classify, use Contact and discuss fit directly.
