Prompting and Tools for Projects and Personal Productivity
60-Minute Interactive Workshop
by Joe Scanlin
The Autonomous Driving Analogy
You're still driving. You're still making the important decisions.
You're just not exhausted by the micro-decisions anymore.
90% reduction in cognitive load = Energy preserved for strategic thinking
By the end: You'll have prompts, patterns, and a daily routine that saves 5+ hours per week.
Separate client data from personal data. Anonymize project details before pasting.
Example: Instead of "The Apple headquarters renovation in Cupertino", use "A 500K sf corporate headquarters renovation in Northern California."
How Large Language Models Work (Simple Version)
An LLM is like an incredibly well-read assistant who's seen billions of examples of text and learned what words tend to follow other words in different contexts.
Key Takeaway: LLMs are prediction engines trained on patterns. That's why good prompts matter—you're giving it better context to make better predictions.
The CRAFT Framework
Every effective prompt includes Context, Role, Action, Format, and Tone
For calendar planning and inbox responses, add this line:
Live Demo Walkthrough
10-Minute Morning Routine
Transform morning chaos into a clear plan in just 10 minutes
Common objections: Budget, schedule, code/certification, maintenance cost, product availability
Meeting ends. You have notes. You need to send a recap, create tasks, and schedule follow-ups. It takes 20 minutes you don't have.
"Discussed two HVAC options. Team leaning toward VRF for flexibility. Budget concern: $80k delta. FM worried about maintenance training. Need vendor quotes by Friday. Code review needed."
Email: "We're moving forward with VRF system pending vendor quotes (due Fri). Budget delta $80k—exploring value engineering. FM training plan needed."
Tasks: Request quotes (Sarah, Fri), code review (Tom, Wed), training plan (Lisa, Mon)
Apply What You've Learned
Use a real project or task from your work. Create:
Remember: Anonymize client details. Use "a 200K sf office building" instead of specific names or addresses.
Share your prompt and output with a partner. Give feedback on: clarity, specificity, guardrails, and whether it solves the right problem.
Create a reusable prompt you can use tomorrow morning (and every morning after).
Add constraints that match your work style:
Pro tip: Save this prompt in a note or doc titled "Morning Routine." Just copy, paste your calendar, and run it daily.
Print this checklist. Put it next to your monitor. Reference it every time you prompt.
Ready-to-use templates for common tasks
The next slides contain 10 prompts you can copy and use immediately. Just replace the {bracketed} sections with your specific details.
Remember: Always anonymize client-specific information before pasting into any AI tool.
You now have the prompts, patterns, and practices to save 5+ hours per week.
Start with one prompt tomorrow. Build from there.
→ Continue to Appendix for deeper insights and tools
Deeper Insights, Tools, and Advanced Strategies
• Before/After Time Audit
• Common Pitfalls & Fixes
• Tool Selection Matrix
• 4-Week Adoption Roadmap
• Client-Facing Output Examples
• Integration with Your Tech Stack
• The 2-Minute Wins
• Error Recovery Patterns
• Team Adoption Playbook
The Real Time Savings (Not Hypothetical)
ROI Calculation: If your billable rate is $150/hr, saving 22 hours/week = $3,300/week or $165K/year in recovered time
Why your prompts aren't working (and what to do)
Fix: Add Context, Role, Action, Format, Tone (CRAFT)
Result: 300-word essay, wrong tone, generic
Result: Concise, appropriate, actionable
Fix: Specify length, audience, structure, tone
Common mistake: "The AI gave me something mediocre, so AI doesn't work."
Reality: AI output is a starting point. Use "write then refine" pattern:
Always verify before using:
Remember: AI assists, you approve.
Decision Matrix for CRE & A&D Work
| Task Type | Best Tool | Why This Tool | Time Saved |
|---|---|---|---|
| Quick drafts (email, summaries) |
ChatGPT or Claude | Fast, conversational, handles ambiguity well | 80% |
| Research with sources (codes, case studies) |
Perplexity | Includes citations, web search integrated | 90% |
| Long documents (proposals, specs) |
Claude | 200K token context, handles large inputs | 75% |
| Meeting transcripts (notes → action items) |
Otter.ai + ChatGPT | Otter captures audio, ChatGPT structures output | 85% |
| Technical specs (product data) |
ChatGPT + ARCAT | ARCAT for data, ChatGPT to format client-facing | 70% |
| Image generation (concept boards) |
DALL-E or Midjourney | Purpose-built for visual content | Variable |
| Workflow automation (email → CRM) |
Zapier or Make | Connects AI outputs to your existing tools | 95% |
Pro Tip: Most professionals use 2-3 tools regularly. Start with ChatGPT or Claude for 90% of tasks, add Perplexity for research. Don't overcomplicate.
Slow and steady wins the race
Common mistake: Trying to use AI for everything on Day 1.
Result: Overwhelm → giving up by Week 2.
Better approach: Start small, prove value to yourself, build momentum.
Real AI outputs you can trust
| Stakeholder | Role | Priority | Evidence They Value |
|---|---|---|---|
| Sarah Chen | VP Facilities | Lifecycle cost, maintenance | TCO analysis, service contracts |
| Marcus Williams | CFO | Budget, ROI timeline | Financial models, payback period |
| Linda Park | Head of Design | Aesthetics, brand alignment | Renderings, material samples |
Prompt used: "Given [3 names and roles], infer decision influence for [200K sf renovation]. Output a table: stakeholder, priority, evidence."
Prompt used: "Draft a 75-word outreach for a facilities VP about an HVAC project. Insight-led opener, warm professional tone, clear next step."
HVAC Selection Meeting – Jan 15, 2025
Decision Made:
Move forward with VRF system for flexibility. Budget delta ($80K) approved pending value engineering review.
Next Actions:
Open Risks:
Lead time for equipment could affect Q2 timeline. Vendor quotes will clarify.
Prompt used: "From these notes, create: 1) decision paragraph, 2) next actions with owners/dates, 3) open risks."
Notice the quality level: These outputs are ready to send (with minor review).
Not "AI slop" — professional, specific, actionable.
This is what's possible when you use CRAFT prompting.
How AI fits into your existing workflow
Advanced: Use Zapier to automate steps 2-3
Time saved: 20 min → 3 min
Time saved: 2 hrs → 20 min
Time saved: 15 min → 2 min
Once you're comfortable with manual AI workflows, consider automating repetitive tasks:
Start here: Master manual prompting first (Weeks 1-4). Then add automation where it makes sense.
Important: You don't need automation to save 10+ hours/week. Manual copy-paste workflows are fast and flexible. Automation is a bonus, not a requirement.
Quickest impact prompts you can try right now
Perfect for: On your phone during a break, between meetings, waiting for a call to start
Each takes ~2 minutes to execute and delivers immediate value
Use case: Boost open rates on client emails
Use case: Run more focused meetings with clear outcomes
Use case: Walk into meetings confident and prepared
Use case: Catch tone problems before you hit send
Use case: Network more effectively without sounding generic
🎯 Challenge: Try one of these TODAY. Pick the lowest-friction option and just do it.
Once you experience the speed, you'll be hooked.
What to do when AI gets it wrong
Reality check: AI will make mistakes. It will hallucinate facts, miss nuance, and occasionally produce garbage. The difference between novices and pros isn't avoiding errors—it's recovering from them quickly.
AI confidently states: "Building code requires X" but you know that's wrong.
Lesson: Always ask for sources on factual claims. AI often admits uncertainty when pressed.
Output is too formal, too casual, or uses jargon your audience won't understand.
Lesson: Be specific about what's wrong. "Make it better" doesn't work. "Make it 30% more conversational" does.
AI gives generic advice that doesn't account for your specific constraints.
Lesson: AI can't read your mind. If output is generic, you didn't provide enough context upfront.
Problem: Output is organized wrong—bullets should be a table, paragraph should be bullets, etc.
Lesson: Specify format upfront in your CRAFT prompt to avoid this.
When to start over:
Solution: Start a new conversation. Sometimes the thread has too much confusing context. Rewrite your prompt with CRAFT, paste into fresh chat, and try again.
How to bring your team along (without forcing it)
The challenge: You're excited about AI, but your team is skeptical, overwhelmed, or worried about job security. How do you create momentum without mandating adoption?
Key: Offer help, don't mandate adoption. Find their pain point (meetings, emails, proposals) and solve it together.
Create a shared doc with 5-7 prompts:
Label each: "Saves ~X minutes" and "Best for [role/task]". Make it copy-paste ready.
Pitch to leadership:
Include: Clear success metrics (hours saved, tasks accelerated), opt-in only, share learnings at the end.
✓ DO
✗ DON'T
Bottom line: Adoption spreads organically when people see results, not when they're told to change.
Your job is to make the first step easy, safe, and valuable.