Signal
The issue is already real, but still weakly structured
The work often starts after a mandate, target, or initiative already exists, but the decision criteria, ownership, or next-step logic are still too unclear.
MandateOwnershipWeak structure
About
Fragment Practice works on AI adoption, review, and operating design in practice.
The studio is most useful when the visible issue looks like AI adoption or transformation, but the harder problem sits in decision criteria, review, responsibility, role boundaries, or the ability to carry work cleanly.
The work focuses on making those foundations clearer so that important work can move with stronger judgment, stronger review, and more workable structure.
Fragment Practice works on issues that are already real but still do not hold together clearly enough. That may mean weak decision criteria, unclear scope, unresolved ownership, mixed requests, weak review, or a path forward that is still too vague to support good work cleanly.
AI is treated here not only as a tooling topic, but as a change in how work is produced, reviewed, governed, and carried across people and systems over time. In practice, the harder work is often deciding what should be automated, what should remain reviewable, and what must stay attributable and clearly owned by people.
The studio therefore works across both sides: the visible surface of AI capability and the operating structure underneath it. The aim is not only to accelerate adoption, but to make the work more workable, reviewable, and better held in practice.
Practice structure
AI changes the surface. The harder work is underneath.
Many AI adoption problems look technical on the surface. In practice, the harder issues often sit in decision criteria, review, responsibility, role boundaries, and the working structure that makes the work more workable in practice.
Reading guide
Left side: AI capability and tools.
Right side: decision criteria, review, responsibility, and role boundaries.
Center: the operating design that makes both sides workable in practice.
How the work usually begins
Three recurring signals.
The studio is often brought in not because nothing is happening, but because the issue has already become real and the structure around it is still too weak.
Signal
Several different problems have been bundled together
AI adoption, governance, review, rollout, service design, and execution support are often being treated as one issue and need to be separated first.
Mixed requestsSeparationClarity
Signal
The work needs boundaries, not only momentum
The harder question is often not only whether AI can be used, but what should be automated, what should remain reviewable, and where responsibility should stay explicit.
BoundariesReviewabilityResponsibility
What the studio works on
Four recurring problem areas.
The practice is organized around recurring kinds of work rather than a long menu of disconnected services.
Focus
Decision criteria and issue structuring
Helping sponsors, owners, and planning teams clarify what the issue is, what should be decided, and what should happen next.
Decision criteriaScopeNext steps
Focus
AI governance and operating boundaries
Clarifying responsibility, review, control, and where automation should stop when AI changes how work is produced, checked, and carried in practice.
ResponsibilityReviewAutomation boundary
Focus
Service and operating model structure
Turning a half-formed service, program, or internal push into something clearer in terms of viability, role split, and operating logic.
ViabilityRole splitOperating logic
Focus
Roadmaps and usable working material
Producing material that helps important work move, stay reviewable, and remain usable across people and teams without starting over each time.
RoadmapReviewableWorking material
Founder
The studio is run by Yasuhiro Shinsho.
Yasuhiro Shinsho works on issues where AI adoption, governance, accountability, service design, and operational pressure intersect.
Before founding Fragment Practice, he worked across BIPROGY, KPMG Japan, and NRI Secure Technologies in roles spanning system development, security engineering, IT risk, cybersecurity, operational resilience, governance, and enterprise advisory.
Across those contexts, the same pattern kept returning: important work often stalls not because people do not care, but because decision criteria, review logic, role boundaries, and operating responsibility are still too implicit to support good work over time.
The work now focuses on making those boundaries more explicit: what should be decided, what should be reviewed, what should be traceable, and what must remain clearly owned by people even when AI capability is increasing.
Start here
Choose the entry point that matches the shape of the need.
Use Services when the issue is active and direct support is needed. Use Knowledge when reusable materials or a lighter first step may be enough. Use Writing when you want a clearer frame first. Use Contact when the issue is real but still hard to scope.
Entry points
Four ways into the studio.
About should help you decide where to go next.
Entry point
Services
Use Services when the issue is already active and needs direct help with decision criteria, review, structure, or a workable path forward.
Active issueDirect support
Entry point
Knowledge
Use Knowledge when reusable materials, worksheets, or a lighter first step may be enough before tailored support.
ReusableWorking materialsLighter entry
Entry point
Writing
Use Writing when you want a clearer frame, sharper language, or a better understanding of the issue before deciding how to engage.
FrameLanguageUnderstanding
Entry point
Contact
Use Contact when the issue is real but still hard to scope, classify, or separate into the right kind of support.
FitScopingNext step