FAQ
This page helps you decide whether to use a Knowledge product, compare direct support shapes, send an inquiry, or use Support for product-related issues.
It focuses on fit, service shapes, AI governance support, Knowledge, purchase and refund handling, support, and what kind of work Fragment Practice is actually for.
How to use this page
You do not need perfect certainty before purchasing or reaching out. Use this page to reduce the decision: product, service shape, contact, or support.
Main paths
Knowledge
Structuring Session
Focused Project / AI Governance Sprint
Advisory Support
Contact / Support
Use this page to reduce the next decision
The goal is not to answer everything. It is to help you choose whether to use a product, compare services, ask for support, or send an inquiry.
Look for fit, not perfect certainty
If the issue is real and still difficult to move, that is usually enough signal to choose a starting path.
A short inquiry is acceptable
If the issue is easier to describe than classify, use Contact and explain what is happening now.
Next path
Use this when a reusable product, kit, or working structure may be enough before direct support is needed.
Explore Knowledge
Next path
Use this when the issue is active and you want to compare Structuring Session, Focused Project / AI Governance Sprint, and Advisory Support.
Explore Services
Next path
Use this when the issue is real but still hard to classify, or when you already know which support shape you want to discuss.
Use Contact
Choosing a path
Q1
Use Knowledge when you want a reusable product or kit you can apply yourself. Use Services when the issue is active and you want to compare direct support shapes. Use Contact when the issue is real but still hard to classify, or when you already know which service shape you want to discuss. Use Support for delivery, file access, refund handling, or product-use issues.
Choosing a path
Q2
Choose a Structuring Session when the issue is real but still mixed, unclear, or hard to scope. Choose a Focused Project / AI Governance Sprint when the issue is specific enough to work through over a bounded period and needs decision-ready material, review structure, responsibility boundaries, requirement framing, or management-facing explanation. Choose Advisory Support when new questions keep appearing and the work needs recurring interpretation, review, or judgment support over time.
Choosing a path
Q3
Use Contact and choose service fit or unsure where to start. You do not need to classify the issue first. A short description of what is happening, why it matters, what feels unclear, and what needs to move is enough to begin.
Who this is for
Q4
Fragment Practice is mainly for sponsors, owners, planning leads, AI adoption leads, security or governance leaders, and other people carrying real operating questions around AI adoption, governance, decision quality, review, responsibility, continuity, and workable change.
Fit
Q5
A good fit is usually a live issue that already needs to move, but is still weakly structured. Common examples include unclear ownership, weak review logic, mixed AI adoption and governance questions, unresolved role boundaries, unclear responsibility, missing continuity, or a path forward that is still too vague to support good decisions.
Fit
Q6
This work is not mainly for PMO substitution, continuous execution shoulder work, always-on task management, staff augmentation, broad implementation labor, or generic tool-selection advice. It is strongest when the main need is to clarify decision criteria, strengthen review, structure the issue, define responsibility, and create material people can carry forward.
Services
Q7
A Structuring Session is a focused first step for a live issue that is real but still hard to scope cleanly. It helps separate mixed concerns, surface the actual blockage, clarify decision points, and define the next useful move. It usually leaves behind a compact working memo or equivalent structure.
Services
Q8
A Focused Project / AI Governance Sprint is a bounded engagement for an active AI adoption, governance, security, requirement, review, or operating-design issue. It is used when the issue needs more than one conversation and would benefit from concentrated work that organizes decision-ready material, review logic, responsibility boundaries, requirement framing, operating assumptions, or management-facing explanation over a fixed period.
Services
Q9
Advisory Support is periodic decision and review support for work that changes over time. It is best when new questions, updates, options, risks, or review needs keep appearing and the work needs recurring interpretation and structural adjustment rather than continuous execution support.
Services
Q10
Service pricing is usually shown as representative ranges rather than a strict public rate card. Actual scope depends on the shape of the issue, the density of the work, the cadence, and the material needed. A short inquiry is usually enough to determine whether the work should be a Structuring Session, Focused Project / AI Governance Sprint, Advisory Support, or another path.
AI governance
Q11
AI governance here does not mean only prohibition, policy writing, or abstract principles. It means clarifying how AI can be used in real work: what information can be used, how outputs are reviewed, where human judgment remains necessary, who is responsible, what must be recorded, and how the organization can explain and operate the work safely.
AI governance
Q12
Not only. Rules may be part of the work, but the main focus is making AI-related work usable, reviewable, and accountable in practice. That often means structuring use cases, risk categories, review points, responsibility boundaries, escalation paths, and operating material that can be used by real teams.
AI governance
Q13
Yes, when the need is to turn AI adoption, governance, review, responsibility, and operating questions into material that can support management discussion or decision-making. The work is especially relevant when the organization needs a clear map of use cases, risks, review logic, responsibility, and next steps rather than generic AI trend material.
Process
Q14
Direct support usually starts with a short inquiry through Contact. If the issue is still mixed, a Structuring Session is often the simplest first move. If the issue is already clear enough, it may move toward a Focused Project / AI Governance Sprint or Advisory Support after fit and boundaries are confirmed.
Process
Q15
No. A polished brief is not required. It is enough to describe what is happening now, why it matters, what feels blocked or mixed, and what needs to be decided, reviewed, explained, fixed, or made workable.
Deliverables
Q16
The work usually produces usable material rather than advice alone. Depending on the issue, that may include a decision-oriented memo, AI governance map, requirement brief, responsibility and review map, structure brief, operating note, review setup, or advisory notes that help the work remain understandable and carryable.
Deliverables
Q17
A decision-oriented memo is used to frame the issue, identify key decisions, align decision criteria, compare options and tradeoffs, and clarify next-step paths. It is useful when a live initiative is already moving but the basis for judgment is still too weak.
Deliverables
Q18
An AI governance map organizes how AI use should be understood and reviewed. It may clarify use cases, input information, output use, review points, human judgment, responsibility boundaries, business impact, risk signals, approval logic, and open questions that need to be resolved.
Deliverables
Q19
A responsibility and review map clarifies who decides what, what needs to remain reviewable, where responsibility should stay explicit, and where human judgment, AI use, review, escalation, or control boundaries need to be clearer.
Deliverables
Q20
A structure brief organizes the current state, target state, role split, viability conditions, operating assumptions, and path forward. It is useful when a service, program, platform, AI initiative, or internal push exists but still lacks a workable shape.
Knowledge
Q21
Knowledge is the reusable product layer of Fragment Practice. It provides structured products, kits, and working materials that help reduce ambiguity, improve continuity, or strengthen working structure before direct support is necessary.
Knowledge
Q22
AI Decision Continuity Kit is the first Knowledge product. It is a Markdown-based operating kit for making AI conversations easier to start well, easier to keep in scope, and easier to carry forward across sessions.
Knowledge
Q23
Knowledge gives you reusable products and working files you can use on your own. Services are for live issues that need direct support in context. Knowledge is the lighter product layer. Services are for issue-specific structuring, review, responsibility, and operating design work.
Knowledge
Q24
Often, yes. It is designed as a small and safe first layer. If the main need is better context, clearer scope, and stronger carry-forward across AI conversations, the product may be enough. If the issue later needs adaptation in context, deeper structuring, or recurring review, it is natural to move into direct support.
Purchase
Q25
After purchase, you receive the product by email. Delivery usually includes a download link for the kit and its included files.
Purchase
Q26
Knowledge products are generally delivered by email after payment confirmation. If delivery does not arrive or the link cannot be accessed, use Support.
Purchase
Q27
Yes. Eligible Knowledge products are covered by a 30-day refund policy. If the product is not the right fit, you can request a refund within 30 days of purchase.
Purchase
Q28
If the delivery email did not arrive, the link is broken, or the files are damaged or unreadable, that is a product-support issue. Use Support and include the product name, purchase email, and a short description of the problem.
Purchase
Q29
The standard purchase is best understood as individual or limited internal working use. If you want broader team use, organizational rollout, training use, or internal adaptation at scale, it is better to get in touch first.
Support / Legal
Q30
Contact is for service-fit questions and direct advisory inquiries. Support is for product-related operational issues such as delivery, file access, and refund handling. Legal is the formal page for seller information, licensing scope, payment and delivery basics, refund baseline, and general commercial terms.
Next step
If you want a reusable product layer you can use on your own, start with Knowledge. If the issue is real but still hard to scope, a Structuring Session is often the best first move. If the issue is clear enough to work through over a bounded period, a Focused Project / AI Governance Sprint may fit better. If you need recurring review and decision support, consider Advisory Support. If the issue is still hard to classify, use Contact.
Related paths
Go here to compare Structuring Session, Focused Project / AI Governance Sprint, and Advisory Support as direct support shapes.
Go here for reusable products, working kits, and practical materials that may help before direct support is needed.
Go here for delivery help, file-access issues, refund handling, and product-support boundaries.
Go here for seller information, licensing scope, payment and delivery basics, and general commercial terms.
