# Risey RisePlans Publisher: Roast & Rise Site: https://www.roastandrise.co This file contains the public RisePlan corpus in plain text for AI search, retrieval, and citation. English and Dutch pages share slugs and are paired with hreflang alternates. ## English RisePlans ## AI Readiness Pilot Canonical URL: https://www.roastandrise.co/riseplans/ai-readiness-sprint Subtitle: From scattered experiments to one useful pilot Summary: Choose the workflow where AI can create value now, design the human-in-the-loop routine, and prove in 30 days whether it should scale. Audience: Founders, operators, product leads, and team managers preparing a first serious AI workflow without turning the company into a tool experiment. Outcome: A ranked opportunity map, one selected pilot, a human review routine, risk rules, a live-work exercise, and a 30-day scorecard for scale, redesign, or stop. Course thesis: AI readiness is not a maturity label or a list of tools. It is the operating ability to choose one real workflow, describe the current work clearly, decide where AI may assist, protect human judgment, and measure whether the new routine improves speed, quality, confidence, or customer value. Company workflow: Workflow discovery, pilot selection, human-in-the-loop design, live practice, quality review, and 30-day adoption measurement. Behavior change: Move from scattered individual AI experiments to one owned pilot with explicit inputs, review criteria, quality gates, risk boundaries, and a decision rule for what happens next. Learning outcomes: - Map repeated work by trigger, input, handoff, decision, output, owner, and current friction instead of starting with a tool. - Score AI opportunities by value, workflow clarity, data readiness, risk, and team energy so the first pilot is useful but contained. - Design a human-in-the-loop routine that names what AI drafts or checks, what humans decide, and how feedback improves the workflow. - Run the routine on live work and capture what breaks, what improves, and what must be clarified before asking more people to adopt it. - Use a 30-day scorecard to decide whether the pilot should scale, be redesigned, or stop because the evidence is weak. Chapters: ### 1. Map the Work Find the repeated decisions, documents, handoffs, and customer moments where work slows down or quality varies. Lesson: - Start with the work, not the model. A useful AI pilot usually appears inside a repeated workflow: preparing a proposal, summarizing a customer call, triaging support tickets, drafting a report, comparing research notes, checking a document, or moving context from one person to another. - The best signal is visible friction. Look for delays, repeated copy-paste work, inconsistent quality, missing context, senior people answering the same questions, or customer-facing work that depends too heavily on one person's memory. - A workflow map should name the trigger, inputs, steps, handoffs, decisions, outputs, owner, current pain, and the standard for good work. Without that map, AI adoption becomes opinion-based because nobody can compare before and after. - Do not select the most exciting use case first. Select the workflow where the team can explain the current routine, provide examples, name the risk, and tell whether the result became better. Exercise: Run a 45-minute workflow inventory with one team. List five repeated workflows. For each, capture the trigger, inputs, steps, handoffs, output, owner, current friction, risk level, and what good would look like. Mark where AI might draft, classify, retrieve, summarize, compare, or check quality. End by choosing the two workflows where improvement would be visible within 30 days. Artifact: Workflow map with friction points and candidate AI assists. Worked example: A consulting team notices every proposal starts with the same hunt through old notes, call transcripts, and proof points. The workflow map shows the real bottleneck is not writing. It is missing context before the first draft. Artifact template: - Trigger: what starts this workflow? - Inputs: what information must be available? - Handoffs: who touches the work before it is done? - Friction: where does time, quality, confidence, or context leak? - AI assist: where could AI draft, summarize, compare, classify, or check? Quality checklist: - The map names a repeated workflow, not a broad department. - The current standard for good work is visible. - The proposed AI assist is tied to one workflow moment. Common mistakes: - Listing tools before describing the work. - Choosing a one-off task that will not teach the company anything reusable. Checkpoint: Can someone outside this workflow read the map and understand where the pilot would start? Use at work tomorrow: Pick one live workflow and ask the people inside it: where do we lose the most time, confidence, quality, or context? ### 2. Choose the Pilot Score candidate workflows by practical value, risk, readiness, ownership, and team energy before choosing one move. Lesson: - The right pilot is narrow enough to run and meaningful enough to matter. If it is too broad, nobody owns it. If it is too small, nobody learns anything the company can reuse. - Score each candidate on five dimensions: business value, workflow clarity, available context, risk, and team energy. A strong first pilot has visible value, a clear routine, available examples, manageable risk, and people who want to try. - Avoid pilots where the output cannot be judged. If the team cannot say what a good answer, draft, summary, or decision looks like, AI will only make the ambiguity faster. - A pilot decision memo should also explain what was not selected. This prevents the team from treating every possible AI use case as urgent at the same time. Exercise: Score five opportunities against a readiness matrix. Create a 1-5 score for value, workflow clarity, context availability, risk, and team energy. Write one sentence of evidence for every score. Choose the pilot with the strongest balance and write why the other options are parked, unsafe, too unclear, or better suited for later. Artifact: Pilot decision memo. Worked example: The team scores proposal drafting, support triage, and meeting summaries. Proposal drafting wins because examples are available, quality is reviewable, and a better routine would affect revenue quickly. Artifact template: - Candidate workflow - Value score with evidence - Workflow clarity score with evidence - Context availability score with evidence - Risk score and stop condition - Decision: test now, park, redesign, or reject Quality checklist: - Every score includes one sentence of evidence. - The selected pilot has a named owner. - The memo explains why tempting alternatives are not first. Common mistakes: - Picking the highest-value workflow even when nobody can judge output quality. - Treating every AI idea as urgent. Checkpoint: Would the team still choose this pilot if they had to show the first result in 30 days? Use at work tomorrow: Choose one candidate pilot and write a one-paragraph reason it is worth testing now, including the risk that would make you stop. ### 3. Design the Operating Loop Define the exact routine for requesting AI help, reviewing output, protecting quality, and improving the workflow. Lesson: - AI readiness depends on operating design. The important question is not whether AI can produce output, but how people will request, inspect, improve, and use that output inside the real workflow. - Every pilot needs quality gates. Decide what AI can draft or suggest, what a human must review, what must be escalated, and what should never be automated. Write these rules before the pilot starts. - The loop should be visible: input, AI assist, human review, final decision, feedback, and improvement. If feedback disappears, the workflow will not get better because the team only sees isolated outputs. - Use examples, not only instructions. Show one weak input, one better input, one acceptable output, and one output that must be rejected. This makes quality teachable. Exercise: Write the first human-in-the-loop routine. For the selected pilot, define who starts the workflow, what context AI receives, what AI produces, who reviews it, which quality criteria apply, which claims need checking, what cannot be delegated, and how improvements are logged after each use. Artifact: Pilot operating checklist. Worked example: For proposal drafting, AI creates an outline from discovery notes and proof points. A human checks customer specificity, unsupported claims, scope promises, tone, and next action before anything reaches the prospect. Artifact template: - Workflow trigger - Context AI receives - Output AI may draft or check - Human decision owner - Quality rules - Escalation boundaries - Feedback log Quality checklist: - The human decision cannot be confused with the AI assist. - Claims that need verification are named. - Feedback has a place to go after each use. Common mistakes: - Writing prompts but no review routine. - Letting feedback disappear into private edits. Checkpoint: If the AI output is plausible but wrong, which rule catches it before use? Use at work tomorrow: Write three quality rules that must be checked before any AI-assisted output from this pilot is used in real work. ### 4. Practice on Live Work Use the pilot routine on a real but low-risk work item and record what the first attempt teaches. Lesson: - A pilot becomes useful when it touches live work. Synthetic examples can help training, but they rarely reveal the missing context, unclear ownership, tone problems, and edge cases that block adoption. - Choose a work item with enough realism to matter and low enough risk to recover from mistakes. The first run should create learning, not pressure to prove the whole AI strategy. - Review the result in three layers: input quality, AI output quality, and human decision quality. Often the problem is not the model; it is unclear context, weak examples, or missing review criteria. - Capture changes immediately. If the team waits until the end of the month, the details that would improve the routine will be forgotten. Exercise: Run the routine once on a real work item. Choose one live example. Run the routine from input to final decision. Record what context was missing, what AI handled well, what required human judgment, what quality checks caught, and what should change before the second run. Artifact: Live pilot review note. Worked example: The first live proposal outline saves 20 minutes but invents a proof point. The review note shows the routine needs a required evidence section before the model is allowed to draft claims. Artifact template: - Live work item - Input quality notes - AI output quality notes - Human changes made - Trust, hesitation, and rejection signals - Routine change before the next run Quality checklist: - The practice item is real but recoverable. - The review separates input problems from AI output problems. - At least one routine improvement is captured immediately. Common mistakes: - Practicing only on synthetic examples. - Judging the model without checking whether the input was usable. Checkpoint: What changed in the routine because of this live run? Use at work tomorrow: Test the routine on one low-risk item and ask the reviewer what they trusted, what they changed, and what made them hesitate. ### 5. Measure the First 30 Days Use behavior, speed, quality, adoption, confidence, and business effect signals to decide what happens after the pilot. Lesson: - Measurement should start before the pilot begins. Capture the current baseline so the team can distinguish real improvement from novelty, enthusiasm, or a one-off good result. - Use a small scorecard. Measure speed, quality, adoption, confidence, and business effect. Not every pilot needs a full ROI model, but every pilot needs a decision rule. - The point of 30 days is learning. At the end, decide whether to scale the workflow, redesign the loop, narrow the use case, improve the knowledge base, or stop because the evidence is weak. - Make the decision visible. Teams lose trust when pilots drift. A clear review turns experimentation into operating discipline. Exercise: Create the pilot scorecard and review rhythm. Define three baseline measures, three target measures, a weekly 20-minute review agenda, and one final decision rule. Include one quality measure, one adoption measure, and one business or customer-value signal. Artifact: 30-day pilot scorecard. Worked example: The proposal pilot tracks draft turnaround, reviewer rewrite percentage, salesperson confidence, and whether follow-up quality improves. At day 30, the team scales only if speed improves without lowering specificity. Artifact template: - Baseline measures - Target measures - Weekly review rhythm - Quality signal - Adoption signal - Business or customer-value signal - Scale, redesign, narrow, or stop rule Quality checklist: - The scorecard includes speed and quality, not only activity. - A decision rule exists before the pilot starts. - The final decision can be explained in one paragraph. Common mistakes: - Calling usage adoption even when quality has not improved. - Letting the pilot drift without a day-30 decision. Checkpoint: What evidence would make stopping the pilot the disciplined choice? Use at work tomorrow: Write the one metric and one quality signal that would make this pilot obviously worth continuing. 30-day path: - Week 1: inventory workflows, choose two candidates, and select one pilot with a named owner. - Week 2: write the human-in-the-loop routine, quality gates, examples, and risk boundaries. - Week 3: run the pilot with two to five people on low-risk live work and improve the routine after each use. - Week 4: review the scorecard, decide scale, redesign, or stop, and document what the next workflow can reuse. - After 30 days: convert the pilot into a maintained operating routine only if quality, adoption, and business signals support it. Success signals: - One AI pilot is chosen with a clear owner, workflow, scope, and stop condition. - The team can explain exactly when AI helps, when humans decide, and what quality rules protect the work. - Baseline and target measures exist before broad rollout begins. - At least two live-work reviews improve the routine before any scale decision. - The 30-day review produces a clear scale, redesign, narrow, or stop decision. Reflection prompts: - Where are we experimenting with AI without ownership, quality rules, or a decision moment? - Which workflow would become noticeably better if turnaround, consistency, or context improved? - What output would be risky, embarrassing, or useless if we automated too casually? - What evidence would make this pilot worth scaling beyond the first team? Manager checklist: - Name the pilot owner, reviewer, weekly review moment, and final decision date. - Check that the workflow has baseline measures before testing starts. - Make quality rules and escalation boundaries visible to everyone involved. - Require live-work review notes before adding more people to the pilot. - Decide at day 30: scale, redesign, narrow, or stop. ## Sales Workflow Upgrade Canonical URL: https://www.roastandrise.co/riseplans/sales-workflow-upgrade Subtitle: Sharper proposals, cleaner follow-up, better handoffs Summary: Turn sales research, discovery notes, proposals, follow-up, and handoffs into a repeatable workflow where AI supports preparation and quality without replacing human judgment. Audience: Founders, sales leads, consultants, account managers, and client-facing teams that sell expertise, services, or complex products. Outcome: A practical sales operating system: friction map, voice guide, proposal assist, follow-up rhythm, handoff template, and quality checks for AI-assisted sales work. Course thesis: AI should not make sales feel automated. It should remove low-value preparation work, strengthen specificity, preserve the company's voice, and help the team follow through faster while relationship judgment, commercial choices, and claims stay human-owned. Company workflow: Lead research, discovery capture, sales voice codification, proposal drafting, follow-up, sales-to-delivery handoff, and pipeline quality review. Behavior change: Move from ad hoc sales writing and individual memory to a repeatable workflow with shared voice, clear inputs, review criteria, timely follow-up, and cleaner handoffs. Learning outcomes: - Diagnose where the sales workflow loses time, specificity, trust, or momentum across active and recently closed opportunities. - Turn strong sales examples into a reusable voice guide that protects tone, proof, positioning, and next-step clarity. - Design an AI-assisted proposal routine that transforms discovery notes into a reviewable first draft without inventing claims. - Install a follow-up rhythm that keeps opportunities current, useful, and specific instead of depending on memory. - Create a sales-to-delivery handoff that transfers customer context, promises, risks, and success criteria cleanly. Chapters: ### 1. Find the Revenue Friction Locate the moments where strong opportunities lose specificity, speed, trust, or ownership. Lesson: - Sales workflow problems often hide in transitions: from research to outreach, from discovery to proposal, from proposal to follow-up, and from sold work to delivery. These are the moments where AI can help, but only after the team understands what breaks today. - Use real opportunities, not imagined process diagrams. Recent deals and stalled opportunities show where people waited, repeated work, missed context, wrote generic copy, or failed to make the next step clear. - Separate preparation friction from judgment friction. AI can help gather context, summarize notes, draft structure, and check consistency. It should not decide commercial strategy, make unsupported claims, or replace relationship ownership. - The output of this chapter is a sales friction map that names the step, owner, inputs, customer moment, current pain, and what better work would look like. Exercise: Review five recent opportunities and mark where quality or momentum dropped. For each opportunity, write the customer context, trigger, sales step, next action, delay point, quality issue, missing context, and what better support would have changed. Look for repeated patterns across research, discovery, proposal, follow-up, and handoff. Artifact: Sales friction map. Use at work tomorrow: Open one active opportunity and write the next action that would move it forward with more specificity and less waiting. ### 2. Codify the Sales Voice Turn the team's strongest sales language into reusable examples, prompts, and quality criteria. Lesson: - Generic AI sales output usually appears when the company has not defined its voice. The model fills the gap with average sales language, which can sound polished while weakening trust. - A useful sales voice guide contains examples, not slogans. It should show how the team explains value, handles uncertainty, talks about proof, frames tradeoffs, and asks for the next step. - The guide becomes the quality layer for AI-assisted writing. It tells people what to keep, rewrite, remove, verify, or escalate before anything reaches a prospect. - Include anti-examples. A list of phrases the company would never use is often as valuable as the best examples because it protects tone under time pressure. Exercise: Extract patterns from strong and weak sales artifacts. Choose three strong emails, proposals, or follow-ups and one weak example. Highlight phrases that sound like the company, proof patterns, structure choices, claims that need evidence, and language you would never use. Turn them into seven writing rules and three example rewrites. Artifact: Sales voice guide. Use at work tomorrow: Rewrite one generic follow-up using three rules from the voice guide and compare it to the original. ### 3. Build the Proposal Assist Design a workflow for turning discovery notes into a structured, reviewable proposal draft. Lesson: - The proposal assist should not replace thinking. It should turn messy context into a structured first draft that a salesperson or consultant can judge, improve, and own. - The best inputs are discovery notes, customer goals, constraints, decision criteria, relevant proof, commercial boundaries, delivery assumptions, and the sales voice guide. Weak inputs produce confident but shallow proposals. - Every AI-drafted proposal needs a review checklist for customer specificity, claim support, scope clarity, risks, next action, and language fit. The checklist is what keeps speed from lowering trust. - A strong proposal workflow also records what was changed by the human reviewer. Those edits become better examples for the next draft. Exercise: Create the first proposal drafting prompt and review checklist. Write a prompt that turns discovery notes into a proposal outline with customer goals, recommended approach, proof, scope, risks, and next step. Then create a checklist that verifies specificity, evidence, promise quality, commercial clarity, and tone before the draft can be sent. Artifact: Proposal assist workflow. Use at work tomorrow: Use one discovery note to generate an outline, then review it against the checklist before writing the final proposal. ### 4. Install the Follow-Up Rhythm Make follow-up more timely and useful by connecting context, timing, owner, and next-best action. Lesson: - Follow-up quality is a system, not a memory test. The team needs a rhythm for deciding who needs what, by when, with which context, and why it matters to the opportunity. - AI can help summarize status, draft options, adapt tone, and turn scattered notes into next actions. The owner must still decide the relationship move and check whether the follow-up is useful rather than merely persistent. - A good rhythm makes the pipeline easier to trust because every opportunity has current context, a next step, and an owner. This reduces the invisible cost of stale opportunities. - The best follow-ups add value: a clarified decision, a useful recap, a relevant proof point, a risk removed, or a next conversation made easier. Exercise: Write a weekly pipeline follow-up routine. Create a weekly routine that reviews active opportunities, identifies stalled context, drafts next actions, assigns owners, and marks which follow-ups need human-only judgment. Include a quality check for usefulness, specificity, tone, and next-step clarity. Artifact: Follow-up operating rhythm. Use at work tomorrow: Pick three open opportunities and write one specific, useful follow-up for each before checking tone and next-step clarity. ### 5. Clean the Handoff Transfer customer context, commitments, risks, and success criteria from sales into delivery without losing the story. Lesson: - Sales improvements are incomplete if the handoff stays weak. The customer experience suffers when delivery receives only a contract, a few notes, and a vague promise. - A strong handoff captures customer goals, decision criteria, promised outcomes, stakeholders, risks, open questions, tone signals, commercial boundaries, and what success should look like after the first milestone. - AI can help convert discovery notes and proposal content into a handoff draft, but the salesperson must verify promises and delivery must confirm feasibility. - The handoff is also a learning loop. Delivery feedback should improve future proposals, proof points, qualification, and expectations. Exercise: Create a sales-to-delivery handoff template and test it on one sold project. Use one recent won opportunity. Fill a handoff template with customer context, promised outcomes, stakeholders, decision criteria, delivery risks, first milestone, proof used in sales, and open questions. Ask delivery what context is missing before kickoff. Artifact: Sales-to-delivery handoff template. Use at work tomorrow: Take one active late-stage opportunity and write the handoff notes delivery would need if it closed tomorrow. 30-day path: - Week 1: audit five opportunities and choose the highest-friction sales step to improve first. - Week 2: build the sales voice guide, anti-examples, and review checklist. - Week 3: test proposal and follow-up assists on live opportunities with human review before sending. - Week 4: add the handoff template and measure speed, specificity, follow-through, and delivery readiness. - After 30 days: keep the routines that improve quality and retire prompts that only create faster generic output. Success signals: - Proposal turnaround improves while customer specificity and claim quality stay high. - Follow-ups become more timely, useful, and connected to the customer's actual decision. - The team uses one shared sales voice guide and review checklist. - Sales-to-delivery handoffs include goals, promises, risks, stakeholders, and success criteria. - Pipeline review shows fewer stale opportunities without clear next actions. Reflection prompts: - Where does our sales process currently depend too much on memory or individual style? - Which sales artifact would benefit most from a better first draft and stronger review criteria? - What must always stay human in our sales process? - Where do delivery teams lose context that sales already learned? Manager checklist: - Review the sales voice guide with the people who actually send sales messages. - Test proposal assistance on live but lower-risk opportunities before using it on strategic deals. - Check every AI-assisted claim, proof point, and promise before it reaches a customer. - Measure speed and quality together, not speed alone. - Ask delivery whether the new handoff improves kickoff readiness. ## Company Knowledge System Canonical URL: https://www.roastandrise.co/riseplans/company-knowledge-system Subtitle: Create one trusted version of how the company works Summary: Turn scattered documents, decisions, examples, and team know-how into a maintained company memory people can trust and use in daily work. Audience: Teams that keep answering the same questions, losing context between projects, onboarding slowly, or struggling to make AI useful because knowledge is scattered. Outcome: A practical company memory with a knowledge priority list, navigation map, ownership model, review rhythm, retrieval tests, and rules for what belongs in the system. Course thesis: A company knowledge system is not a prettier folder or a bigger wiki. It is an operating system for keeping decisions, context, workflows, examples, standards, and customer knowledge trustworthy enough for people and AI-assisted workflows to use. Company workflow: Knowledge prioritization, memory mapping, source and ownership design, review routines, retrieval testing, onboarding, and AI-assisted decision support. Behavior change: Move from scattered knowledge and repeated questions to a maintained company memory with owners, review dates, source clarity, retrieval quality, and explicit rules for stale or uncertain information. Learning outcomes: - Decide which knowledge is durable, high-value, and repeated enough to belong in the company memory. - Design a simple memory map that reflects how the company actually sells, delivers, decides, and improves. - Assign ownership, source rules, review triggers, and confidence labels so trust does not decay quietly. - Create the first high-value entries using examples, decisions, templates, and operating routines from real work. - Test whether people and AI-assisted workflows can retrieve answers with enough accuracy, source clarity, and usefulness. Chapters: ### 1. Define What Must Be Remembered Separate durable company knowledge from temporary notes, chat history, and low-value archive material. Lesson: - The first mistake is saving everything. A strong company memory starts by deciding what must remain true, findable, and reviewable over time. - Durable knowledge includes offers, customer segments, positioning, process, decisions, examples, standards, operating routines, pricing logic, delivery rules, and lessons learned. Temporary discussion belongs somewhere else. - The best starting point is repeated questions. If people keep asking the same thing, the company has already revealed a knowledge gap that costs time and consistency. - Prioritization matters because knowledge systems fail when teams try to migrate the whole archive before proving usefulness. Start with the questions that block work today. Exercise: List the ten questions people repeatedly ask. Collect repeated questions from chat, meetings, onboarding, sales, delivery, operations, and leadership. For each question, write who asks it, why it matters, what a good answer must include, where the answer currently lives, and what breaks when the answer is missing or wrong. Artifact: Knowledge priority list. Use at work tomorrow: Ask three teammates which question they are tired of answering and where they currently look for the answer. ### 2. Design the Memory Map Create a structure for offers, customers, process, decisions, examples, culture, and operating routines. Lesson: - A company memory needs a map people can understand without training. If the structure is too abstract, the system becomes another place to search and abandon. - Use categories that match the business: what we sell, who we serve, how we work, what we decided, what good looks like, what changed, and what needs review. - The map should support action. Every section should help someone decide, write, onboard, sell, deliver, support, manage risk, or improve quality. - Design for retrieval, not storage. A useful map includes names people would search for, example questions each section answers, and links between related decisions and workflows. Exercise: Draft the first navigation model for company knowledge. Create five to seven top-level sections. Under each, add three example entries, the real question each entry should answer, likely owner, source of truth, and review trigger. Test whether a teammate can place five messy documents into the map. Artifact: Company memory map. Use at work tomorrow: Create a one-page draft of the memory map and test whether a teammate can find where three real entries belong. ### 3. Assign Trust and Ownership Decide who owns each knowledge area, how sources are shown, and how stale information gets corrected. Lesson: - Knowledge quality is an ownership problem. If nobody owns an entry, everyone eventually distrusts it, and AI-assisted workflows amplify the confusion. - Each important entry needs an owner, a backup owner, source links, a review rhythm, and a visible last-reviewed date. This makes uncertainty manageable instead of hidden. - Ownership should follow expertise and workflow, not hierarchy. The person closest to the knowledge should usually maintain it, while leadership owns decisions that set direction. - Add confidence labels for entries that are draft, inferred, outdated, or waiting for approval. A useful system can say 'we do not know yet' without pretending. Exercise: Assign owners, sources, and review dates to the first ten entries. For each priority entry, assign an owner, backup owner, source link, review date, confidence status, and trigger that means the entry must be updated sooner. Mark which entries are safe for AI-assisted retrieval and which need human confirmation. Artifact: Knowledge ownership table. Use at work tomorrow: Choose one high-value entry and add an owner, source, confidence status, and next review date. ### 4. Create Useful Entries Turn raw knowledge into pages, templates, examples, and decision records that people can actually use. Lesson: - A useful knowledge entry is not just a note. It answers a real question, explains when it applies, shows examples, names the owner, and tells people what to do next. - The strongest entries combine a short answer, context, examples, source links, related decisions, and update rules. This makes the knowledge usable for humans and safer for AI-assisted workflows. - Templates and examples matter because they reveal what good looks like. Without examples, teams keep asking for clarification or recreate work in different styles. - Start with a small set of high-value entries and improve them through use. A living memory is built by answering real work, not by perfecting taxonomy in isolation. Exercise: Write three high-value memory entries from the priority list. For each entry, include the question it answers, short answer, context, examples, owner, source, last-reviewed date, related entries, and what someone should do if the answer seems wrong. Ask one teammate to use each entry on real work. Artifact: First company memory entries. Use at work tomorrow: Turn one repeated question into a complete memory entry with source, owner, and example. ### 5. Make Retrieval Trustworthy Test whether stored knowledge produces answers, templates, decisions, and onboarding support people can trust. Lesson: - A knowledge system is only useful if retrieval produces answers people trust. Test it with real questions, not with happy-path demos. - Good retrieval gives answer, source, confidence, context, and next action. It should distinguish confirmed fact from interpretation and flag when a human owner should verify. - Every failed search is product feedback. Use failures to improve naming, structure, examples, owner assignment, and stale content rules. - For AI-assisted retrieval, require source visibility. The system should make it easy to inspect where an answer came from before it becomes a customer message, decision, or internal standard. Exercise: Test five real questions against the knowledge system. Ask five common questions and score the answers for accuracy, completeness, source clarity, confidence, and usefulness. For every weak answer, decide whether the fix is content, structure, ownership, naming, review rhythm, or tooling. Artifact: Retrieval quality checklist. Use at work tomorrow: Test one real onboarding or customer question and note exactly where the answer breaks down. 30-day path: - Week 1: identify repeated questions, critical decisions, and the first ten high-value knowledge entries. - Week 2: build the memory map, owner model, source rules, and confidence labels. - Week 3: create the first entries and test them against live sales, delivery, onboarding, or operations questions. - Week 4: run retrieval tests, fix weak answers, and install the review rhythm. - After 30 days: expand only after the team trusts the first entries and owners keep them current. Success signals: - Repeated high-value questions are answered from one trusted place. - Every critical entry has an owner, source, confidence status, and review date. - New team members can find core context without interrupting the same people repeatedly. - AI-assisted answers cite maintained entries rather than scattered or stale material. - Retrieval tests produce specific fixes instead of vague complaints that the wiki is messy. Reflection prompts: - Which company knowledge is most painful when it is missing, stale, or wrong? - Where do people currently go first when they need an answer, and why? - What would make the team trust an answer from the knowledge system? - Which knowledge should not be used by AI without human confirmation? Manager checklist: - Choose the first ten high-value entries, not the whole archive. - Assign owners, sources, confidence labels, and review dates before scaling. - Test retrieval with real team questions every week for the first month. - Remove, update, or mark stale content instead of letting trust erode. - Require source visibility for AI-assisted knowledge use. ## Manager Habits for AI Adoption Canonical URL: https://www.roastandrise.co/riseplans/manager-habits-ai-adoption Subtitle: Turn experiments into team routines Summary: Help managers turn private AI experiments into shared team routines, quality standards, visible learning loops, and adopted workflow changes. Audience: Managers and team leads who need to guide AI adoption practically without becoming tool police, hype translators, or the only person responsible for quality. Outcome: A manager operating rhythm for adoption: baseline scan, weekly learning loop, judgment coaching, workflow standard, reinforcement plan, and quality review habits. Course thesis: AI adoption becomes real when managers convert individual experiments into shared routines, judgment standards, visible learning loops, and workflow improvements. The manager's job is not to force tool usage; it is to help the team choose useful work, practice safely, inspect quality, and standardize what proves valuable. Company workflow: Team adoption baseline, use-case selection, weekly learning ritual, quality coaching, workflow standardization, adoption reinforcement, and behavior review. Behavior change: Move from private AI experimentation and uneven confidence to team-level habits that improve work, make quality expectations visible, and turn useful experiments into maintained routines. Learning outcomes: - Assess where the team is experimenting, blocked, confident, skeptical, duplicating effort, or carrying quality risk. - Choose one team workflow where AI practice can improve real work without creating unsafe shortcuts. - Run a lightweight weekly ritual that shares useful examples, failures, prompts, review criteria, and next experiments. - Coach people to judge AI output for accuracy, specificity, tone, context, risk, and usefulness. - Turn repeated wins into team standards with triggers, inputs, steps, examples, owners, and review rules. Chapters: ### 1. Set the Adoption Baseline Understand who is experimenting, who is blocked, where quality concerns show up, and which workflows deserve attention first. Lesson: - Managers need a clear baseline before pushing adoption. Otherwise the loudest experimenters define the story while quieter blockers, skeptics, and quality concerns stay invisible. - The baseline should capture use cases, confidence, blockers, risks, repeated questions, and workflows people want to improve. It should not become a performance review or a tool-compliance exercise. - Look for patterns across the team: people using AI privately, people avoiding it because expectations are unclear, people worried about quality, and people repeating experiments others have already tried. - The goal is to know what support is needed: permission, examples, shared prompts, quality standards, safer tools, clearer workflow choices, or a manager decision about what not to automate. Exercise: Run a short team adoption scan. Ask each team member what they have tried, where AI helped, where it failed, what they are unsure about, which workflow they want to improve next, and what would make them trust the output. Summarize patterns without naming people. Artifact: AI adoption baseline. Use at work tomorrow: Ask the team one question: where could AI help this week if we had a safe way to test it? ### 2. Choose the Team Workflow Pick one routine where shared AI practice can improve real work instead of encouraging random individual experimentation. Lesson: - Team adoption improves when practice is attached to a workflow everyone recognizes. Random tool experimentation creates anecdotes, but workflow practice creates reusable operating knowledge. - Choose a routine with visible friction, repeatable inputs, manageable risk, and a clear definition of good work. Examples include meeting summaries, customer follow-up, research synthesis, status updates, document review, or internal knowledge retrieval. - The chosen workflow should be small enough to practice this month and useful enough that people care. If the work has no owner or quality standard, start there before introducing AI. - Make the behavior change explicit. The goal might be faster preparation, clearer summaries, better first drafts, more consistent review, or fewer repeated questions. Exercise: Select one workflow and write the behavior change. From the adoption baseline, choose three candidate workflows. Score each on value, repeatability, risk, clarity, and team energy. Select one and write the current behavior, desired behavior, owner, quality standard, and first practice moment. Artifact: Team workflow choice memo. Use at work tomorrow: Name one workflow the team will practice together and one workflow that is explicitly out of scope for now. ### 3. Create the Weekly Learning Loop Make AI learning visible through small demos, shared prompts, honest failure review, and next experiments. Lesson: - Adoption spreads through visible examples. A weekly loop turns isolated experiments into shared team learning and reduces the shame people can feel when outputs are rough. - Keep the ritual small. One useful example, one failed attempt, one reusable pattern, and one next experiment is enough. The point is rhythm, not a meeting about AI for its own sake. - The manager's role is to lower the emotional cost of learning while raising the quality bar. People need permission to show rough attempts and enough structure to improve them. - Capture what the team learns. The best prompt, input example, review criterion, or failure pattern should become part of the workflow standard instead of disappearing after the meeting. Exercise: Design a 20-minute weekly AI learning ritual. Write a recurring agenda with four parts: useful example, failed attempt, reusable pattern, and next test. Assign a rotating owner, define what artifact gets saved, and choose how the team will update quality rules after each session. Artifact: Team learning loop agenda. Use at work tomorrow: Schedule the first 20-minute learning loop and ask one person to bring a real example with both the input and output. ### 4. Coach for Judgment Teach people when to trust, check, rewrite, escalate, or ignore AI output. Lesson: - The skill that matters is judgment. Teams need to know how to inspect AI output for accuracy, specificity, tone, missing context, risk, and usefulness. - Managers can coach this by reviewing real outputs with clear criteria instead of giving abstract AI advice. Ask what is true, what is missing, what sounds off, what needs a source, and what decision still belongs to a human. - Good judgment creates confidence. People learn when AI is useful, when it needs revision, when more context is required, and when the work should stay human. - Review both the input and the output. Many weak AI results come from vague instructions, missing examples, unclear target audience, or no quality standard. Exercise: Review three AI-assisted outputs with quality criteria. Pick three examples from the chosen team workflow. Score each on factuality, specificity, tone, completeness, risk, and actionability. Decide what should be kept, rewritten, checked, escalated, or discarded. Then improve the input for one example and compare the result. Artifact: Judgment coaching checklist. Use at work tomorrow: Review one AI-assisted output with a teammate and ask what evidence would make it trustworthy enough to use. ### 5. Turn Wins Into Standards Convert repeated useful experiments into operating routines the team can adopt and maintain. Lesson: - Experiments create value only when the team captures what worked. Otherwise every person starts again from zero and adoption becomes a collection of private tricks. - A standard should explain trigger, inputs, steps, examples, prompts or tools, quality checks, owner, and what to do when the output is uncertain or risky. - Do not standardize too early. Wait until an experiment has repeated usefulness and a clear quality routine. A standard created from one lucky result will collapse under real variation. - Reinforcement matters. Managers should review whether the standard is used, whether it improves the work, and whether it needs updating as the team learns. Exercise: Write one standard operating routine from a successful experiment. Choose one experiment that saved time or improved quality at least twice. Document when to use it, required context, steps, examples, quality checks, owner, failure modes, and review rhythm. Ask the team to test it for one week. Artifact: AI workflow standard. Use at work tomorrow: Turn one useful prompt or workflow into a shared team note with trigger, input, quality checklist, and owner. 30-day path: - Week 1: run the adoption baseline, identify blockers, and select one team workflow for shared practice. - Week 2: start the weekly learning loop and capture examples, failures, and reusable patterns. - Week 3: coach judgment with real outputs from the chosen workflow and improve the quality checklist. - Week 4: standardize one useful routine and decide how managers will reinforce, review, and update it. - After 30 days: expand to another workflow only after the first routine has evidence of use and quality improvement. Success signals: - Managers can name the team's current AI use cases, blockers, risks, and highest-value workflow. - The team has a weekly routine for sharing what works, what failed, and what will be tested next. - People use shared quality criteria to review AI output instead of accepting or rejecting it by instinct. - At least one experiment becomes a documented team standard with trigger, inputs, examples, and owner. - The manager can point to a behavior change in real work, not only more tool usage. Reflection prompts: - Who on the team is already experimenting, and who is quietly blocked or skeptical? - Which workflow would benefit from shared practice instead of private experimentation? - What quality risks make people hesitant to use AI? - Which experiment deserves to become a team standard, and what evidence proves it? Manager checklist: - Run the adoption baseline without turning it into evaluation. - Choose one workflow and one behavior change before asking for broader adoption. - Create a weekly learning ritual with real examples and honest failure review. - Coach quality judgment using actual outputs and explicit criteria. - Standardize only the workflows that prove useful more than once. ## Dutch RisePlans ## AI Readiness Pilot Canonical URL: https://www.roastandrise.co/nl/riseplans/ai-readiness-sprint Subtitle: Van losse experimenten naar een bruikbare pilot Summary: Kies de workflow waar AI nu waarde kan maken, ontwerp de human-in-the-loop routine, en bewijs binnen 30 dagen of de pilot schaal verdient. Audience: Founders, operators, productleads en teammanagers die een eerste serieuze AI-workflow willen starten zonder van het bedrijf een tooltest te maken. Outcome: Een geprioriteerde opportunity map, een gekozen pilot, reviewroutine, risicoregels, live-work oefening en 30-dagen scorecard voor schaal, redesign of stop. Course thesis: AI readiness is geen volwassenheidslabel. Het is het vermogen om een echte workflow te kiezen, het huidige werk helder te beschrijven, te bepalen waar AI mag helpen, menselijk oordeel te beschermen en te meten of de nieuwe routine snelheid, kwaliteit, vertrouwen of klantwaarde verbetert. Company workflow: Workflow discovery, pilotkeuze, human-in-the-loop ontwerp, live oefenen, kwaliteitsreview en 30-dagen adoptiemeting. Behavior change: Van losse individuele AI-experimenten naar een pilot met eigenaar, inputs, reviewcriteria, kwaliteitsregels, risicogrenzen en een duidelijk besluitmoment. Learning outcomes: - Herhaald werk in kaart brengen op trigger, input, overdracht, besluit, output, eigenaar en frictie. - AI-kansen scoren op waarde, workflowhelderheid, data readiness, risico en teamenergie. - Een human-in-the-loop routine ontwerpen waarin duidelijk is wat AI doet en wat mensen beslissen. - De routine testen op live werk en vastleggen wat breekt, verbetert of verduidelijking nodig heeft. - Een 30-dagen scorecard gebruiken om te kiezen voor schaal, redesign of stop. Chapters: ### 1. Breng het werk in kaart Vind de herhaalde besluiten, documenten, overdrachten en klantmomenten waar werk vertraagt of kwaliteit wisselt. Lesson: - Begin bij het werk, niet bij het model. Een bruikbare AI-pilot verschijnt meestal in een terugkerende workflow zoals voorstellen maken, support triage, onderzoek samenvatten of context overdragen. - De beste aanwijzing is zichtbare frictie: wachten, copy-paste, wisselende kwaliteit, ontbrekende context of senior mensen die dezelfde vragen blijven beantwoorden. - Een workflowmap noemt trigger, inputs, stappen, overdrachten, besluiten, output, eigenaar, pijn en standaard voor goed werk. Exercise: Run een workflow-inventaris van 45 minuten met een team. Noem vijf herhaalde workflows. Leg per workflow trigger, inputs, stappen, overdrachten, output, eigenaar, frictie, risico en definitie van goed vast. Kies de twee workflows waar verbetering binnen 30 dagen zichtbaar kan zijn. Artifact: Workflowmap met frictiepunten en kandidaat AI-assists. Use at work tomorrow: Kies een live workflow en vraag het team waar tijd, vertrouwen, kwaliteit of context weglekt. ### 2. Kies de pilot Score kandidaat-workflows op waarde, risico, readiness, eigenaarschap en teamenergie voordat je een eerste move kiest. Lesson: - De juiste pilot is smal genoeg om te draaien en belangrijk genoeg om van te leren. - Score elke kandidaat op businesswaarde, workflowhelderheid, beschikbare context, risico en teamenergie. - Vermijd pilots waar niemand kan beoordelen of de output goed is. AI versnelt anders vooral de onduidelijkheid. Exercise: Score vijf kansen tegen een readiness matrix. Geef elke kans een 1-5 score voor waarde, helderheid, context, risico en energie. Schrijf per score een bewijszin. Kies de pilot met de beste balans en leg uit waarom de andere opties worden geparkeerd. Artifact: Pilot decision memo. Use at work tomorrow: Schrijf voor een kandidaat-pilot in een alinea waarom hij nu de moeite waard is, inclusief het risico dat je zou laten stoppen. ### 3. Ontwerp de operating loop Definieer hoe AI-hulp wordt gevraagd, output wordt beoordeeld, kwaliteit wordt beschermd en feedback terug de workflow in gaat. Lesson: - De vraag is niet alleen of AI output kan maken. De vraag is hoe mensen die output aanvragen, inspecteren, verbeteren en gebruiken in echt werk. - Elke pilot heeft kwaliteitsregels nodig. Schrijf op wat AI mag concepten, wat mensen beslissen, wat geescaleerd wordt en wat niet geautomatiseerd mag worden. - Gebruik voorbeelden: zwakke input, betere input, acceptabele output en output die moet worden afgewezen. Exercise: Schrijf de eerste human-in-the-loop routine. Leg vast wie start, welke context AI krijgt, wat AI oplevert, wie reviewt, welke criteria gelden, welke claims check nodig hebben en hoe verbeteringen worden gelogd. Artifact: Pilot operating checklist. Use at work tomorrow: Schrijf drie kwaliteitsregels die altijd gecheckt worden voordat AI-assisted output live gebruikt mag worden. ### 4. Oefen op live werk Gebruik de pilotroutine op een echt werkitem met laag risico en leg vast wat de eerste run leert. Lesson: - Een pilot wordt nuttig wanneer hij live werk raakt. Testvoorbeelden missen vaak de context, eigenaarschap en randgevallen die adoptie blokkeren. - Review het resultaat in lagen: inputkwaliteit, AI-output en menselijk oordeel. - Leg wijzigingen meteen vast. Aan het einde van de maand zijn de details vaak verdwenen. Exercise: Run de routine een keer op een echt werkitem. Kies een live voorbeeld. Doorloop de routine van input tot besluit. Noteer ontbrekende context, wat AI goed deed, waar menselijk oordeel nodig was en wat voor de tweede run moet veranderen. Artifact: Live pilot review note. Use at work tomorrow: Test de routine op een laag-risico item en vraag de reviewer wat vertrouwen gaf, wat is aangepast en waar twijfel bleef. ### 5. Beslis na 30 dagen Gebruik bewijs uit gebruik om te kiezen of de pilot schaalt, smaller wordt, opnieuw ontworpen wordt of stopt. Lesson: - Een pilot zonder besluitmoment wordt snel een extra gewoonte. Spreek vooraf af wat bewijs genoeg is om door te gaan. - Meet snelheid en kwaliteit samen. Sneller werk dat vertrouwen verlaagt is geen winst. - Documenteer wat de volgende workflow kan hergebruiken: context, reviewregels, voorbeelden, eigenaarschap en stopcondities. Exercise: Maak de 30-dagen scorecard. Leg baseline, doel, gebruik, kwaliteitsobservaties, risico's, teamfeedback en klant- of businesssignalen naast elkaar. Sluit af met scale, redesign, narrow of stop. Artifact: 30-dagen pilot scorecard. Use at work tomorrow: Kies een metric en een kwaliteitsignaal voordat de pilot breder wordt gebruikt. 30-day path: - Week 1: inventariseer workflows, kies twee kandidaten en selecteer een pilot met eigenaar. - Week 2: schrijf de reviewroutine, kwaliteitsregels, voorbeelden en risicogrenzen. - Week 3: test met twee tot vijf mensen op laag-risico live werk en verbeter na elke run. - Week 4: review de scorecard en besluit schaal, redesign, narrow of stop. - Na 30 dagen: onderhoud de routine alleen als kwaliteit, adoptie en businesssignalen dat ondersteunen. Success signals: - Een AI-pilot is gekozen met eigenaar, scope, workflow en stopconditie. - Het team kan uitleggen wanneer AI helpt, wanneer mensen beslissen en welke kwaliteitsregels gelden. - Baseline en doelmetingen bestaan voordat bredere uitrol begint. - Minstens twee live-work reviews verbeteren de routine. - De 30-dagen review levert een duidelijk besluit op. Reflection prompts: - Waar experimenteren we met AI zonder eigenaar, kwaliteitsregels of besluitmoment? - Welke workflow wordt merkbaar beter als snelheid, consistentie of context verbetert? - Welke output wordt riskant of nutteloos als we te casual automatiseren? - Welk bewijs maakt deze pilot schaalwaardig? Manager checklist: - Noem eigenaar, reviewer, reviewmoment en einddatum. - Check dat de workflow baseline measures heeft. - Maak kwaliteitsregels en escalatiegrenzen zichtbaar. - Vraag live-work review notes voordat meer mensen aansluiten. - Beslis op dag 30: schaal, redesign, narrow of stop. ## Sales Workflow Upgrade Canonical URL: https://www.roastandrise.co/nl/riseplans/sales-workflow-upgrade Subtitle: Scherpere voorstellen, betere opvolging, schonere overdracht Summary: Maak van sales research, discovery notes, voorstellen, follow-up en overdracht een herhaalbare workflow waarin AI voorbereiding en kwaliteit ondersteunt zonder menselijk oordeel te vervangen. Audience: Founders, sales leads, consultants, accountmanagers en klantgerichte teams die expertise, diensten of complexe producten verkopen. Outcome: Een praktisch sales operating system: frictiemap, voice guide, proposal assist, follow-up ritme, overdrachtsformat en kwaliteitschecks. Course thesis: AI moet sales niet geautomatiseerd laten voelen. Het moet laagwaardig voorbereidingswerk verlagen, specificiteit versterken, de stem van het bedrijf beschermen en follow-through versnellen terwijl relatieoordeel, commerciele keuzes en claims menselijk blijven. Company workflow: Lead research, discovery capture, sales voice, proposal drafting, follow-up, sales-to-delivery overdracht en pipeline kwaliteitsreview. Behavior change: Van ad hoc sales writing en individuele geheugensteuntjes naar een gedeelde workflow met voice, inputs, reviewcriteria, tijdige follow-up en schonere overdracht. Learning outcomes: - Zien waar sales snelheid, specificiteit, vertrouwen of momentum verliest. - Sterke salesvoorbeelden omzetten in een reusable voice guide. - Een AI-assisted proposal routine ontwerpen die geen claims verzint. - Een follow-up ritme installeren dat context actueel houdt. - Customer context en beloftes schoner overdragen naar delivery. Chapters: ### 1. Vind omzetfrictie Lokaliseer de momenten waar sterke kansen specificiteit, snelheid, vertrouwen of eigenaarschap verliezen. Lesson: - Salesproblemen zitten vaak in overgangen: research naar outreach, discovery naar voorstel, voorstel naar follow-up en verkoop naar delivery. - Gebruik echte kansen. Recente deals en stalled opportunities laten zien waar mensen wachtten, context misten of generieke copy schreven. - Scheid voorbereidingsfrictie van oordeelsfrictie. AI mag context verzamelen en structureren. Relatiekeuzes blijven menselijk. Exercise: Review vijf recente opportunities en markeer waar momentum of kwaliteit zakte. Schrijf per opportunity klantcontext, trigger, salesstap, next action, vertraging, kwaliteitsissue, ontbrekende context en wat betere support had veranderd. Artifact: Sales frictiemap. Use at work tomorrow: Open een actieve opportunity en schrijf de next action die hem specifieker en sneller vooruit helpt. ### 2. Codeer de sales voice Zet de sterkste sales-taal van het team om in voorbeelden, prompts en reviewcriteria. Lesson: - Generieke AI-salescopy ontstaat vaak wanneer de voice niet is vastgelegd. - Een goede voice guide bevat voorbeelden, tradeoffs, proof patterns en woorden die je juist vermijdt. - De guide wordt de kwaliteitslaag voor AI-assisted schrijven. Exercise: Haal patronen uit sterke en zwakke sales artifacts. Kies drie sterke mails, voorstellen of follow-ups en een zwak voorbeeld. Markeer toon, bewijs, structuur, claims die check nodig hebben en taal die je nooit gebruikt. Artifact: Sales voice guide. Use at work tomorrow: Herschrijf een generieke follow-up met drie regels uit de voice guide. ### 3. Bouw de proposal assist Ontwerp een workflow die discovery notes omzet in een gestructureerde, reviewbare eerste versie. Lesson: - De proposal assist vervangt het denken niet. Hij maakt rommelige context beoordeelbaar. - Sterke inputs zijn discovery notes, klantdoelen, constraints, decision criteria, proof, commerciele grenzen en voice guide. - Elke draft heeft review nodig op klant-specificiteit, claims, scope, risico, next action en tone of voice. Exercise: Maak de eerste proposal prompt en reviewchecklist. Schrijf een prompt die discovery notes omzet in een outline met doelen, aanpak, bewijs, scope, risico en next step. Maak daarna een checklist voor specificity, evidence, promises en toon. Artifact: Proposal assist workflow. Use at work tomorrow: Gebruik een discovery note om een outline te maken en review die voordat je het voorstel schrijft. ### 4. Installeer follow-up ritme Maak follow-up tijdiger en nuttiger door context, timing, eigenaar en next-best action te verbinden. Lesson: - Follow-up kwaliteit is een systeem, geen geheugentest. - AI kan status samenvatten, opties drafts maken en notities omzetten in acties. De eigenaar beslist de relatiemove. - Goede follow-ups voegen waarde toe: recap, bewijs, risico omlaag of een gesprek makkelijker maken. Exercise: Schrijf een wekelijkse pipeline follow-up routine. Maak een routine voor actieve opportunities, stalled context, next actions, eigenaren en checks op nut, specificiteit, toon en helderheid. Artifact: Follow-up operating rhythm. Use at work tomorrow: Kies drie open opportunities en schrijf per stuk een specifieke, nuttige follow-up. ### 5. Maak de overdracht schoon Draag klantcontext, beloftes, risico's en succescriteria over zonder het verhaal kwijt te raken. Lesson: - Salesverbetering is incompleet als delivery alleen een contract en losse notities krijgt. - Een sterke handoff bevat doelen, criteria, stakeholders, risico's, open vragen, tone signals en succes na de eerste mijlpaal. - AI kan een handoff draft maken. Sales checkt beloftes en delivery checkt haalbaarheid. Exercise: Maak een sales-to-delivery handoff template en test hem op een gewonnen project. Gebruik een recente gewonnen opportunity. Vul klantcontext, promises, stakeholders, risico's, first milestone en open vragen in. Vraag delivery welke context mist. Artifact: Sales-to-delivery handoff template. Use at work tomorrow: Schrijf voor een late-stage opportunity de overdrachtsnotities die delivery morgen nodig zou hebben. 30-day path: - Week 1: audit vijf opportunities en kies de salesstap met de meeste frictie. - Week 2: bouw voice guide, anti-examples en reviewchecklist. - Week 3: test proposal en follow-up assists op live opportunities met menselijke review. - Week 4: voeg de handoff template toe en meet snelheid, specificiteit en overdrachtskwaliteit. - Na 30 dagen: behoud routines die kwaliteit verhogen en verwijder prompts die alleen sneller generiek maken. Success signals: - Proposal turnaround verbetert terwijl specificiteit en claimkwaliteit hoog blijven. - Follow-ups zijn tijdiger, nuttiger en verbonden met de echte klantbeslissing. - Het team gebruikt een gedeelde voice guide en reviewchecklist. - Handoffs bevatten doelen, beloftes, risico's, stakeholders en succescriteria. - Pipeline review toont minder stale opportunities zonder next action. Reflection prompts: - Waar hangt sales te veel aan geheugen of individuele stijl? - Welk sales artifact heeft het meest aan een betere eerste draft? - Wat moet altijd menselijk blijven in ons salesproces? - Waar raakt delivery context kwijt die sales al had geleerd? Manager checklist: - Review de voice guide met de mensen die salesberichten sturen. - Test proposal assist op live maar lager-risico opportunities. - Check elke AI-assisted claim voordat die naar een klant gaat. - Meet snelheid en kwaliteit samen. - Vraag delivery of de nieuwe handoff kickoff-readiness verbetert. ## Company Knowledge System Canonical URL: https://www.roastandrise.co/nl/riseplans/company-knowledge-system Subtitle: Een betrouwbare versie van hoe het bedrijf werkt Summary: Zet verspreide documenten, besluiten, voorbeelden en teamkennis om in een onderhouden bedrijfsgeheugen dat mensen in dagelijks werk kunnen vertrouwen. Audience: Teams die dezelfde vragen blijven beantwoorden, context verliezen tussen projecten, langzaam onboarden of moeite hebben om AI nuttig te maken omdat kennis versnipperd is. Outcome: Een praktisch bedrijfsgeheugen met prioriteitenlijst, navigatiemodel, ownership, reviewritme, retrieval tests en regels voor wat erin hoort. Course thesis: Een company knowledge system is geen mooiere folder of grotere wiki. Het is een operating system om beslissingen, context, workflows, voorbeelden, standaarden en klantkennis betrouwbaar genoeg te houden voor mensen en AI-assisted workflows. Company workflow: Kennisprioritering, memory mapping, bron- en ownershipdesign, reviewroutines, retrieval testing, onboarding en AI-assisted decision support. Behavior change: Van verspreide kennis en herhaalde vragen naar een onderhouden geheugen met eigenaren, reviewdatums, bronhelderheid, retrievalkwaliteit en regels voor stale informatie. Learning outcomes: - Bepalen welke kennis duurzaam, waardevol en herhaald genoeg is. - Een memory map ontwerpen die past bij verkopen, leveren, beslissen en verbeteren. - Ownership, bronnen, reviewtriggers en confidence labels vastleggen. - Eerste entries maken uit echte voorbeelden, besluiten en routines. - Testen of mensen en AI antwoorden kunnen terugvinden met bronhelderheid en genoeg vertrouwen. Chapters: ### 1. Bepaal wat onthouden moet worden Scheid duurzame bedrijfskennis van tijdelijke notes, chatgeschiedenis en laagwaardige archieven. Lesson: - De eerste fout is alles bewaren. Sterk bedrijfsgeheugen begint met kiezen wat waar, vindbaar en reviewbaar moet blijven. - Begin bij herhaalde vragen. Als mensen hetzelfde blijven vragen, heeft het bedrijf de kennisgap al aangewezen. - Prioriteit voorkomt dat een kennissysteem een migratieproject wordt voordat het nut heeft bewezen. Exercise: List de tien vragen die mensen steeds opnieuw stellen. Verzamel vragen uit chat, meetings, onboarding, sales, delivery en operations. Schrijf per vraag wie hem stelt, waarom hij telt, waar het antwoord nu leeft en wat breekt als het antwoord mist. Artifact: Knowledge priority list. Use at work tomorrow: Vraag drie teamgenoten welke vraag ze moe zijn om te beantwoorden en waar ze nu zoeken. ### 2. Ontwerp de memory map Maak een structuur voor aanbod, klanten, proces, besluiten, voorbeelden, cultuur en routines. Lesson: - Een bedrijfsgeheugen heeft een kaart nodig die mensen zonder training snappen. - Gebruik categorieen die bij de business passen: wat we verkopen, wie we bedienen, hoe we werken, wat we besloten, wat goed is en wat review nodig heeft. - Ontwerp voor retrieval, niet voor opslag. Exercise: Schets het eerste navigatiemodel. Maak vijf tot zeven hoofdsecties. Voeg per sectie voorbeeldentries, eigenaar, source of truth en reviewtrigger toe. Test of een teamgenoot vijf rommelige documenten kan plaatsen. Artifact: Company memory map. Use at work tomorrow: Maak een eenpagina-map en test waar drie echte entries horen. ### 3. Geef vertrouwen en ownership Bepaal wie elk kennisgebied bezit, hoe bronnen zichtbaar zijn en hoe stale informatie wordt gecorrigeerd. Lesson: - Kenniskwaliteit is een ownershipprobleem. Zonder eigenaar verdwijnt vertrouwen langzaam. - Belangrijke entries hebben eigenaar, backup, source links, reviewritme en last-reviewed datum nodig. - Confidence labels maken onzekerheid zichtbaar zonder te doen alsof alles zeker is. Exercise: Wijs owners, bronnen en reviewdatums toe aan de eerste tien entries. Geef elke priority entry een eigenaar, backup, bronlink, reviewdatum, confidence status en trigger voor update. Markeer wat veilig is voor AI-assisted retrieval. Artifact: Knowledge ownership table. Use at work tomorrow: Kies een high-value entry en voeg owner, source, confidence status en next review date toe. ### 4. Maak bruikbare entries Zet ruwe kennis om in pagina's, templates, voorbeelden en decision records die mensen echt gebruiken. Lesson: - Een goede entry beantwoordt een echte vraag, zegt wanneer hij geldt, toont voorbeelden en noemt de eigenaar. - Sterke entries combineren kort antwoord, context, voorbeelden, bronlinks, verwante besluiten en update-regels. - Begin klein en verbeter door gebruik. Exercise: Schrijf drie high-value memory entries. Neem per entry de vraag, het korte antwoord, context, voorbeelden, owner, source, last-reviewed datum en related entries op. Laat iemand de entry gebruiken op echt werk. Artifact: Eerste company memory entries. Use at work tomorrow: Maak van een herhaalde vraag een complete memory entry met bron, owner en voorbeeld. ### 5. Maak retrieval betrouwbaar Test of opgeslagen kennis antwoorden, templates, besluiten en onboarding support oplevert die mensen vertrouwen. Lesson: - Een kennissysteem is pas nuttig als retrieval antwoorden geeft die mensen kunnen controleren. - Goed retrieval toont antwoord, bron, confidence, context en next action. - Elke mislukte zoekactie is productfeedback voor naamgeving, structuur, voorbeelden, ownership of stale content. Exercise: Test vijf echte vragen tegen het kennissysteem. Score antwoorden op accuracy, volledigheid, source clarity, confidence en nut. Bepaal per zwak antwoord of de fix content, structuur, ownership, naming, reviewritme of tooling is. Artifact: Retrieval quality checklist. Use at work tomorrow: Test een echte onboarding- of klantvraag en noteer waar het antwoord breekt. 30-day path: - Week 1: identificeer herhaalde vragen, kritieke besluiten en de eerste tien high-value entries. - Week 2: bouw memory map, ownermodel, sourceregels en confidence labels. - Week 3: maak de eerste entries en test ze tegen live sales-, delivery-, onboarding- of operationsvragen. - Week 4: run retrieval tests, fix zwakke antwoorden en installeer het reviewritme. - Na 30 dagen: breid uit nadat het team de eerste entries vertrouwt. Success signals: - Herhaalde high-value vragen worden uit een vertrouwde plek beantwoord. - Elke kritieke entry heeft owner, source, confidence status en reviewdatum. - Nieuwe teamleden vinden kerncontext zonder steeds dezelfde mensen te onderbreken. - AI-assisted antwoorden citeren onderhouden entries. - Retrieval tests leveren concrete fixes op. Reflection prompts: - Welke bedrijfskennis doet het meeste pijn wanneer die ontbreekt, stale is of fout staat? - Waar zoeken mensen nu als eerste naar een antwoord? - Wat maakt dat het team een antwoord uit het systeem vertrouwt? - Welke kennis mag AI niet gebruiken zonder menselijke bevestiging? Manager checklist: - Kies de eerste tien high-value entries, niet het hele archief. - Wijs owners, sources, confidence labels en reviewdatums toe voordat je schaalt. - Test retrieval wekelijks met echte teamvragen. - Verwijder, update of markeer stale content. - Eis bronzichtbaarheid voor AI-assisted kennisgebruik. ## Manager Habits for AI Adoption Canonical URL: https://www.roastandrise.co/nl/riseplans/manager-habits-ai-adoption Subtitle: Maak van experimenten teamroutines Summary: Help managers om prive-experimenten met AI om te zetten in gedeelde teamroutines, kwaliteitsstandaarden, zichtbare leerlussen en workflowverandering. Audience: Managers en teamleads die AI-adoptie praktisch moeten begeleiden zonder toolpolitie, hypevertaler of enige kwaliteitsbewaker te worden. Outcome: Een manager operating rhythm voor adoptie: baseline scan, wekelijkse learning loop, judgment coaching, workflow standard, reinforcement plan en quality review habits. Course thesis: AI-adoptie wordt echt wanneer managers individuele experimenten omzetten in gedeelde routines, judgment standards, zichtbare leerlussen en workflowverbeteringen. De taak is niet toolgebruik afdwingen. De taak is nuttig werk kiezen, veilig oefenen, kwaliteit inspecteren en standaardiseren wat bewijs levert. Company workflow: Team adoption baseline, use-case selectie, wekelijkse learning ritual, quality coaching, workflow standardization, reinforcement en behavior review. Behavior change: Van prive-experimenten en ongelijke confidence naar teamgewoonten die werk verbeteren, kwaliteit zichtbaar maken en nuttige experimenten onderhouden. Learning outcomes: - Zien wie experimenteert, blokkeert, twijfelt, risico draagt of dubbel werk doet. - Een teamworkflow kiezen waar AI-practice echt werk verbetert. - Een licht weekritueel draaien met voorbeelden, mislukkingen, prompts en reviewcriteria. - Mensen coachen om AI-output te beoordelen op juistheid, specificiteit, toon, context, risico en nut. - Herhaalde wins omzetten in teamstandaarden met triggers, inputs, voorbeelden en owners. Chapters: ### 1. Zet de adoptiebaseline Begrijp wie experimenteert, wie blokkeert, waar kwaliteit schuurt en welke workflows aandacht verdienen. Lesson: - Managers hebben een baseline nodig voordat ze adoptie duwen. Anders bepaalt de luidste experimenter het verhaal. - De scan hoort use cases, confidence, blockers, risico's en workflowwensen te tonen zonder performance review te worden. - Het doel is weten welke support nodig is: toestemming, voorbeelden, prompts, kwaliteitsstandaarden, veiligere tools of scherpere keuzes. Exercise: Run een korte team adoption scan. Vraag ieder teamlid wat ze geprobeerd hebben, waar AI hielp, waar het faalde, waar twijfel zit, welke workflow ze willen verbeteren en wat output betrouwbaar zou maken. Vat patronen samen zonder mensen te labelen. Artifact: AI adoption baseline. Use at work tomorrow: Vraag het team: waar kan AI deze week helpen als we een veilige testvorm hebben? ### 2. Kies de teamworkflow Kies een routine waar gezamenlijke AI-practice echt werk verbetert in plaats van losse tooltests te stimuleren. Lesson: - Adoptie groeit sneller wanneer practice vastzit aan een herkenbare workflow. - Kies een routine met zichtbare frictie, herhaalbare inputs, beheersbaar risico en een duidelijke definitie van goed werk. - Maak de gedragsverandering expliciet: sneller voorbereiden, duidelijker samenvatten, consistenter reviewen of minder herhaalde vragen. Exercise: Selecteer een workflow en schrijf de gedragsverandering. Kies drie kandidaat-workflows uit de baseline. Score ze op waarde, herhaalbaarheid, risico, helderheid en teamenergie. Selecteer een en beschrijf huidig gedrag, gewenst gedrag, eigenaar en eerste oefenmoment. Artifact: Team workflow choice memo. Use at work tomorrow: Noem een workflow die het team samen oefent en een workflow die nu buiten scope blijft. ### 3. Maak de weekly learning loop Maak AI-leren zichtbaar met kleine demos, gedeelde prompts, eerlijke failure review en volgende experimenten. Lesson: - Adoptie verspreidt via zichtbare voorbeelden. Een wekelijkse loop maakt private experimenten teamleren. - Houd het klein: een nuttig voorbeeld, een mislukking, een patroon en een volgende test. - Leg vast wat geleerd is, zodat prompts, inputs en reviewcriteria onderdeel worden van de workflow. Exercise: Ontwerp een AI-learning ritual van 20 minuten. Schrijf een agenda met useful example, failed attempt, reusable pattern en next test. Kies een roterende owner, artifact en manier om quality rules bij te werken. Artifact: Team learning loop agenda. Use at work tomorrow: Plan de eerste 20 minuten en vraag iemand een echt voorbeeld met input en output mee te nemen. ### 4. Coach voor oordeel Leer mensen wanneer ze AI-output vertrouwen, checken, herschrijven, escaleren of negeren. Lesson: - De kernvaardigheid is oordeel. Teams moeten output inspecteren op juistheid, specificiteit, toon, ontbrekende context, risico en nut. - Coach met echte outputs en criteria. Vraag wat waar is, wat mist, wat bron nodig heeft en welke beslissing menselijk blijft. - Review input en output. Zwakke resultaten komen vaak uit vage instructies of ontbrekende voorbeelden. Exercise: Review drie AI-assisted outputs met quality criteria. Score elk voorbeeld op factuality, specificity, tone, completeness, risk en actionability. Bepaal wat blijft, herschreven, gecheckt, geescaleerd of weggegooid wordt. Artifact: Judgment coaching checklist. Use at work tomorrow: Review een AI-assisted output met een teammate en vraag welk bewijs hem betrouwbaar genoeg maakt. ### 5. Maak wins tot standaarden Zet herhaalde nuttige experimenten om in routines die het team kan adopteren en onderhouden. Lesson: - Experimenten leveren pas blijvende waarde als het team vastlegt wat werkte. - Een standaard beschrijft trigger, inputs, stappen, voorbeelden, tools, quality checks, owner en wat te doen bij onzekerheid. - Standaardiseer pas nadat iets herhaald nuttig is en een duidelijke kwaliteitsroutine heeft. Exercise: Schrijf een operating routine uit een succesvol experiment. Kies een experiment dat minstens twee keer tijd bespaarde of kwaliteit verbeterde. Documenteer wanneer het gebruikt wordt, context, stappen, voorbeelden, checks, owner, failure modes en reviewritme. Artifact: AI workflow standard. Use at work tomorrow: Maak van een nuttige prompt of workflow een teamnote met trigger, input, quality checklist en owner. 30-day path: - Week 1: run de baseline, identificeer blockers en kies een teamworkflow. - Week 2: start de learning loop en leg voorbeelden, failures en patronen vast. - Week 3: coach oordeel met echte outputs en verbeter de quality checklist. - Week 4: standaardiseer een nuttige routine en bepaal hoe managers reviewen en bijwerken. - Na 30 dagen: breid pas uit nadat de eerste routine gebruik en kwaliteitsverbetering laat zien. Success signals: - Managers kennen use cases, blockers, risico's en de hoogste-waarde workflow van het team. - Het team heeft een wekelijkse routine voor wat werkt, wat faalde en wat getest wordt. - Mensen gebruiken gedeelde quality criteria om AI-output te beoordelen. - Minstens een experiment wordt een gedocumenteerde teamstandaard. - De manager kan gedrag in echt werk aanwijzen, niet alleen meer toolgebruik. Reflection prompts: - Wie experimenteert al, en wie is stil geblokkeerd of sceptisch? - Welke workflow vraagt om gedeelde practice in plaats van prive-experimenten? - Welke kwaliteitsrisico's maken mensen terughoudend? - Welk experiment verdient een teamstandaard, en welk bewijs laat dat zien? Manager checklist: - Run de baseline zonder er beoordeling van te maken. - Kies een workflow en een gedragsverandering voor bredere adoptie. - Maak een learning ritual met echte voorbeelden en eerlijke failure review. - Coach oordeel met concrete output en expliciete criteria. - Standaardiseer alleen workflows die meer dan eens nuttig blijken.