FAQ
This page covers the main questions people usually have before deciding whether to purchase a product, reach out, or choose a starting point.
It focuses on fit, services, Knowledge, product purchase, 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. If one of these answers is enough to help you choose a next step, that is enough. If not, use Contact and describe the situation directly.
Covers
Who this helps
Products and services
Purchase and refund questions
Fit, scope, and next step
Use this page to choose the next move
The point is not to answer everything. It is to reduce ambiguity enough to know where to go next.
A short description is enough
If the issue is easier to describe than to classify, that is still enough reason to get in touch.
Look for fit, not perfect certainty
If the issue is already real and still hard to move, that is usually the right level of signal.
Who this is for
Q1
Fragment Practice is mainly for people carrying real operating questions around AI adoption, decision quality, review, continuity, and workable change. That often includes AI adoption leaders, people responsible for productivity improvement or organizational change, and sponsors or owners carrying an initiative that still needs clearer structure, stronger review, or a more workable path forward.
Fit
Q2
A good fit is usually a real issue that already needs to move, but is still weakly structured. Common examples include unclear ownership, weak review logic, mixed requests, unresolved role boundaries, missing continuity, or a path forward that is still too vague to support good decisions.
Starting point
Q3
Start with Knowledge when you want a smaller, reusable operating layer you can apply yourself. Start with a Structuring Session when the issue is real but still hard to scope, separate, or frame. Start with a Focused Project when the issue is clear enough to work through over a short period and turn into decision-ready material. Start with Advisory when the issue needs ongoing review, prioritization, and structural adjustment over time. Start with Writing when you want a clearer frame first. Start with Contact when the issue is real but still hard to classify.
Knowledge
Q4
Knowledge is the reusable layer of Fragment Practice. It is meant to make AI-supported work more continuous, reviewable, and reusable by helping you externalize context, keep one real direction in scope, and carry useful work forward across sessions.
Knowledge
Q5
AI Decision Continuity Kit is the first Knowledge product and the current OS layer in the line. 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
Q6
Knowledge gives you reusable guidance, structures, and working files you can use on your own. Services are for live issues that need direct support in context. Knowledge helps you build continuity and working structure. Services help you work through a specific issue that is already active, pressured, or too context-dependent for a general product alone.
Knowledge
Q7
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
Q8
After purchase, you receive the product by email. Delivery usually includes a download link for the Markdown-based kit and its included files.
Purchase
Q9
Knowledge products are generally delivered by email after payment confirmation. If delivery does not arrive or the link cannot be accessed, use the Support page or Contact.
Purchase
Q10
Yes. 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
Q11
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 the Support page or Contact and include the product name, purchase email, and a short description of the problem.
Purchase
Q12
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.
Services
Q13
A Structuring Session is a focused first session used to clarify the issue, separate mixed concerns, surface the real blockage, and define the next useful move. It is often the best starting point when the issue is real but still hard to scope cleanly.
Services
Q14
A Focused Project is short-term, concentrated work on a specific issue, structure, or operating question. It is used when the issue needs more than one conversation and benefits from a tightly scoped engagement that organizes, designs, and documents decision-ready material over a fixed period.
Services
Q15
Advisory is periodic decision support for review, prioritization, and structural adjustment. It is best when the issue needs ongoing checkpoints, external judgment, and continuity over time rather than continuous execution support.
Deliverables
Q16
The work usually produces usable material rather than advice alone. Depending on the layer, that may include a working kit, decision memo, structure brief, roadmap, responsibility model, or review setup.
Deliverables
Q17
A decision memo is used to frame the issue, identify key decisions, align decision criteria, and clarify next-step options. It is useful when a live initiative is already moving but the basis for judgment is still too weak.
Deliverables
Q18
A structure brief is used to organize the current state, target state, role split, viability conditions, and operating assumptions. It is useful when a service, program, or internal push exists but still lacks a workable structure.
Deliverables
Q19
A roadmap is used to sequence the work, surface dependencies, define milestones, and set review points. It is useful when the issue is understood well enough that the next challenge is deciding how to move it forward in a realistic order.
Fit
Q20
This work is not mainly for PMO substitution, continuous execution shoulder work, always-on task management, or broad implementation labor. It is strongest when the main need is to clarify decision criteria, strengthen review, structure the issue, and create material people can actually carry forward.
Process
Q21
For products, it starts with a direct purchase. For direct support, work often starts with a Structuring Session or a short inquiry through Contact. The aim is to clarify the actual blockage, separate mixed concerns, surface the decision criteria, and decide whether a Focused Project, Advisory, or another next step makes sense.
Pricing
Q22
No. Service pricing is usually shown as representative ranges rather than a strict rate card. Actual scope depends on the shape of the issue, the density of the work, and the kind of material needed. A short conversation is usually enough to size the engagement.
Support / Legal
Q23
Support is for product-related issues such as delivery, file access, and refund handling. Legal is the formal page for seller information, licensing scope, payment and delivery basics, refund boundary, and general commercial terms.
Next step
If you want a reusable operating layer you can use on your own, start with Knowledge. If the issue is real but still hard to scope, start with a Structuring Session. If the issue is clear enough to work through over a short period, a Focused Project may fit better. If you need recurring review and decision support, move to Advisory. If the issue is still hard to classify, use Contact.
Related pages
Go here for the OS-layer product and future reusable products for more continuous AI-supported work.
Go here when the issue is active and direct help is needed with structure, decision criteria, review, or a workable path forward.
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.
