chihlasm
a955888acf
Move 9 completed/historical docs from root to docs/archive/: - ARCHITECTURE.md, BACKLOG.md, CLAUDE-SETUP.md, MICHAEL-NOTES.md - IMPLEMENTATION-SUMMARY-ISSUE-34.md, PHASE-2.5-PERSONAL-BRANCHING.md - REBRAND-IMPLEMENTATION-GUIDE.md, TS-EXAMPLES.md, WORKSPACE-REMOVAL-PLAN.md Move QUICK-START.md to docs/ Add previously untracked files: - DEV-ENV.md (devserver01 setup guide) - docs/marketing/ (one-pager HTML + PDF) - docs/ResolutionFlow_Pivot_Architecture.docx Update CLAUDE.md rebrand guide reference path. Deleted temp files: .temp_fixed.py, .temp_fixed2.py, ai_provider_*.py, ai_provider.patch, test_write.txt Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
456 lines
14 KiB
Markdown
456 lines
14 KiB
Markdown
# Backlog - Future Features & Ideas
|
|
|
|
> **Purpose:** Long-term feature ideas, "what if" concepts, and parking lot items.
|
|
> **Note:** These are brainstorm items, not committed roadmap. Evaluate based on user demand and business impact.
|
|
> **Last Updated:** February 2, 2026
|
|
|
|
---
|
|
|
|
## Table of Contents
|
|
|
|
1. [Dynamic Script Generation](#dynamic-script-generation)
|
|
2. [Beyond Service Desk - Department Expansion](#beyond-service-desk---department-expansion)
|
|
3. [Tree Collaboration & Sharing](#tree-collaboration--sharing)
|
|
4. [Integration Ideas](#integration-ideas)
|
|
5. [Mobile & Accessibility](#mobile--accessibility)
|
|
6. [Gamification & Training](#gamification--training)
|
|
7. [Advanced Analytics](#advanced-analytics)
|
|
8. [AI-Powered Features](#ai-powered-features)
|
|
9. [Parking Lot - Quick Ideas](#parking-lot---quick-ideas)
|
|
10. [Long-Term Vision](#long-term-vision)
|
|
11. [Idea Evaluation Criteria](#idea-evaluation-criteria)
|
|
|
|
---
|
|
|
|
## Dynamic Script Generation
|
|
|
|
### Concept: Trees That Generate PowerShell Scripts
|
|
|
|
Instead of just guiding a tech through troubleshooting steps, trees could COLLECT information and OUTPUT executable scripts.
|
|
|
|
**Example Scenario: New User Onboarding**
|
|
|
|
A ticket comes in: "New hire starting Monday - John Smith, Marketing department"
|
|
|
|
Traditional approach:
|
|
1. Tech manually creates AD user
|
|
2. Tech looks up which groups Marketing needs
|
|
3. Tech adds user to groups one by one
|
|
4. Tech moves user to correct OU
|
|
5. Tech documents what they did
|
|
|
|
**Script Generation approach:**
|
|
|
|
```
|
|
┌─────────────────────────────────────────────────────────────┐
|
|
│ NEW USER ONBOARDING TREE │
|
|
├─────────────────────────────────────────────────────────────┤
|
|
│ Step 1: Enter user details │
|
|
│ First Name: [John_____________] │
|
|
│ Last Name: [Smith____________] │
|
|
│ Department: [Marketing________] ▼ │
|
|
│ │
|
|
│ Step 2: Select required groups (auto-suggested by dept) │
|
|
│ ☑ Domain Users │
|
|
│ ☑ Marketing-All │
|
|
│ ☑ SharePoint-Marketing │
|
|
│ │
|
|
│ Step 3: Confirm organizational unit │
|
|
│ OU Path: OU=Marketing,OU=Users,DC=contoso,DC=com │
|
|
│ │
|
|
│ [Generate Script] │
|
|
└─────────────────────────────────────────────────────────────┘
|
|
```
|
|
|
|
**Generated Output:**
|
|
|
|
```powershell
|
|
# New User Creation Script
|
|
# Generated by Patherly - 2026-01-28 14:32
|
|
# Ticket: #12345
|
|
|
|
$Password = Read-Host -AsSecureString "Enter initial password"
|
|
New-ADUser -Name "John Smith" `
|
|
-GivenName "John" `
|
|
-Surname "Smith" `
|
|
-SamAccountName "jsmith" `
|
|
-UserPrincipalName "jsmith@contoso.com" `
|
|
-Path "OU=Marketing,OU=Users,DC=contoso,DC=com" `
|
|
-AccountPassword $Password `
|
|
-Enabled $true
|
|
|
|
# Add to groups
|
|
@("Domain Users", "Marketing-All", "SharePoint-Marketing") | ForEach-Object {
|
|
Add-ADGroupMember -Identity $_ -Members "jsmith"
|
|
}
|
|
```
|
|
|
|
**Value Proposition:**
|
|
- Eliminates manual typing errors
|
|
- Ensures consistency across techs
|
|
- Auto-documents what was done
|
|
- Reduces training time for new hires
|
|
- Script can be reviewed before execution (safety)
|
|
|
|
### Other Script Generation Use Cases
|
|
|
|
| Use Case | Inputs Collected | Output |
|
|
|----------|------------------|--------|
|
|
| User Offboarding | Username, actions to take | Disable/remove script |
|
|
| Bulk Group Changes | User list, groups | Group membership script |
|
|
| Computer Setup | Name, department, user | Deployment script |
|
|
| Network Diagnostics | Issue description | Diagnostic collection script |
|
|
| M365 License Assignment | User, license type | PowerShell for M365 |
|
|
|
|
### Technical Considerations
|
|
|
|
**New Node Type: "Input Node"**
|
|
```typescript
|
|
interface InputNode {
|
|
type: 'input';
|
|
fields: InputField[];
|
|
validation?: ValidationRules;
|
|
next_node_id: string;
|
|
}
|
|
|
|
interface InputField {
|
|
name: string;
|
|
label: string;
|
|
type: 'text' | 'select' | 'multiselect' | 'checkbox' | 'number';
|
|
options?: string[];
|
|
variable_name: string; // used in script template
|
|
}
|
|
```
|
|
|
|
**New Node Type: "Script Output Node"**
|
|
```typescript
|
|
interface ScriptOutputNode {
|
|
type: 'script_output';
|
|
script_template: string; // PowerShell with {{variable}} placeholders
|
|
language: 'powershell' | 'bash' | 'python';
|
|
documentation_template?: string;
|
|
}
|
|
```
|
|
|
|
### Safety & Compliance Features
|
|
|
|
- **Script Review Mode:** Scripts NEVER auto-execute, always presented for review
|
|
- **Audit Trail:** Log which scripts were generated and by whom
|
|
- **Template Approval:** Senior engineers review templates before publishing
|
|
- **Environment Variables:** Store org-specific values (domain name, OU paths)
|
|
|
|
### Implementation Phases
|
|
|
|
1. **Phase 1:** Basic script output with variable substitution
|
|
2. **Phase 2:** Input collection nodes with validation
|
|
3. **Phase 3:** Smart defaults (department → group suggestions)
|
|
4. **Phase 4:** Direct execution capability (Enterprise, with approval workflows)
|
|
|
|
---
|
|
|
|
## Beyond Service Desk - Department Expansion
|
|
|
|
### Concept: Department-Specific Path Libraries
|
|
|
|
The "guided decision tree" concept applies to ANY process that benefits from consistency and documentation.
|
|
|
|
**Target Departments:**
|
|
|
|
| Department | Use Cases |
|
|
|------------|-----------|
|
|
| Service Desk | Troubleshooting (current focus) |
|
|
| Sales | Quoting, assessments, discovery |
|
|
| vCIO/Consulting | Policy creation, strategic planning |
|
|
| Onboarding | Client setup, documentation gathering |
|
|
| Finance | Contract review, billing disputes |
|
|
| HR | Employee onboarding, policy acknowledgment |
|
|
|
|
### vCIO / Consulting: Policy Builder
|
|
|
|
Guide clients through policy creation with smart templates and boilerplate language.
|
|
|
|
**Example: Acceptable Use Policy Builder**
|
|
|
|
User selects sections to include:
|
|
- ☑ Computer Use Policy
|
|
- ☑ Mobile Device Policy
|
|
- ☑ BYOD Policy
|
|
- ☑ AI Usage Policy
|
|
- ☑ Remote Work Policy
|
|
|
|
**Generated Output:** Complete, formatted policy document (Word/PDF) with:
|
|
- Professional boilerplate language
|
|
- Industry-specific compliance notes (HIPAA for healthcare, etc.)
|
|
- Signature/acknowledgment section
|
|
|
|
**Policy Types to Support:**
|
|
- Acceptable Use Policy (AUP)
|
|
- Information Security Policy
|
|
- Password Policy
|
|
- Data Classification Policy
|
|
- Incident Response Policy
|
|
- BYOD Policy
|
|
- AI/Generative AI Policy
|
|
|
|
**Value Proposition:**
|
|
- vCIOs generate client policies in minutes, not hours
|
|
- Consistent, professional output
|
|
- Industry-specific compliance built-in
|
|
- Upsell opportunity: "Policy Review" as a service
|
|
|
|
### Sales: Quote Builder & Assessment Paths
|
|
|
|
Guide sales reps through discovery with consistent methodology that surfaces upsell opportunities.
|
|
|
|
**Assessment Types:**
|
|
|
|
1. **Security Assessment** - Endpoint protection, MFA, training gaps
|
|
2. **Backup Assessment** - Frequency, retention, testing procedures
|
|
3. **Hardware Assessment** - Workstation age, server infrastructure, warranties
|
|
4. **Compliance Assessment** - HIPAA, PCI, documentation status
|
|
5. **Cloud Readiness Assessment** - Migration complexity, bandwidth needs
|
|
|
|
**Generated Outputs:**
|
|
- Gap Analysis Report (client-facing)
|
|
- Quote Worksheet (internal)
|
|
- Proposal Content (client-facing)
|
|
|
|
### Client Onboarding Paths
|
|
|
|
Structured onboarding ensuring nothing is missed:
|
|
- Contact gathering (technical, billing, decision makers)
|
|
- Credentials collection (secure vault integration)
|
|
- Documentation intake (passwords, network diagrams)
|
|
- Standards configuration (naming conventions, security policies)
|
|
- Tool deployment checklist
|
|
- Handoff to service desk
|
|
|
|
**Output:** Populated documentation templates, IT Glue/Hudu import-ready data
|
|
|
|
---
|
|
|
|
## Tree Collaboration & Sharing
|
|
|
|
### Public Tree Gallery
|
|
|
|
- Users publish trees to community gallery
|
|
- Rating and review system
|
|
- "Verified" badge for quality trees
|
|
- Fork and customize
|
|
|
|
### Tree Marketplace
|
|
|
|
- Premium trees from experts
|
|
- Revenue share model (70/30)
|
|
- Subscription access to premium library
|
|
|
|
### Tree Inheritance
|
|
|
|
- Company-wide "official" trees
|
|
- Teams create local variations
|
|
- Changes can be proposed upstream
|
|
- Version control and diff viewing
|
|
|
|
---
|
|
|
|
## Integration Ideas
|
|
|
|
### PSA Deep Integration
|
|
|
|
- Create ticket from tree resolution
|
|
- Auto-populate ticket fields from session
|
|
- Link session to existing ticket
|
|
- Pull ticket context into tree suggestions
|
|
|
|
**Target PSAs:** ConnectWise, Kaseya, Autotask, ServiceNow
|
|
|
|
### RMM Integration
|
|
|
|
- Pull device info into tree context
|
|
- "This computer has X installed, skip to step Y"
|
|
- Trigger RMM scripts from tree actions
|
|
- Asset-aware troubleshooting
|
|
|
|
**Target RMMs:** Datto, ConnectWise Automate, NinjaRMM
|
|
|
|
### Documentation Integration
|
|
|
|
- Link tree nodes to IT Glue/Hudu articles
|
|
- Auto-create documentation from resolved sessions
|
|
- Sync tree content with knowledge base
|
|
|
|
### Communication Integration
|
|
|
|
- Slack/Teams notifications for escalations
|
|
- Share session summary to channel
|
|
- Request help from team within tree
|
|
|
|
---
|
|
|
|
## Mobile & Accessibility
|
|
|
|
### Mobile App (PWA Enhancement)
|
|
|
|
- Offline tree access
|
|
- Voice input for hands-free use
|
|
- Camera integration for error screenshots
|
|
- Push notifications for shared sessions
|
|
|
|
### Voice-Guided Mode
|
|
|
|
- Read steps aloud
|
|
- Voice commands to navigate
|
|
- Useful for field techs with hands busy
|
|
- Accessibility for vision-impaired users
|
|
|
|
---
|
|
|
|
## Gamification & Training
|
|
|
|
### Tech Leaderboards
|
|
|
|
- Trees completed
|
|
- Resolution time improvements
|
|
- Contribution to tree improvements
|
|
- Points and badges
|
|
|
|
### Training Mode
|
|
|
|
- Practice trees without affecting stats
|
|
- Simulated scenarios
|
|
- Quiz mode with wrong-path feedback
|
|
- Certification preparation
|
|
|
|
### Onboarding Tracks
|
|
|
|
- Structured learning paths for new hires
|
|
- Progress tracking
|
|
- Manager visibility into training progress
|
|
|
|
---
|
|
|
|
## Advanced Analytics
|
|
|
|
### Predictive Issue Alerts
|
|
|
|
- "VPN issues spike on Mondays after updates"
|
|
- Proactive notifications to prepare
|
|
- Trend forecasting
|
|
|
|
### Cost Attribution
|
|
|
|
- Estimate time spent per issue type
|
|
- Calculate cost of common problems
|
|
- ROI justification for fixes
|
|
|
|
### Comparative Analytics
|
|
|
|
- Benchmark against anonymized industry data
|
|
- "Your password reset time is 20% faster than average"
|
|
- Identify improvement opportunities
|
|
|
|
---
|
|
|
|
## AI-Powered Features
|
|
|
|
### Conversational Interface
|
|
|
|
- Chat with AI about an issue
|
|
- AI suggests relevant trees
|
|
- Natural language navigation
|
|
|
|
### Auto-Tree Generation
|
|
|
|
- Record a senior tech explaining a fix
|
|
- AI generates tree structure from transcript
|
|
- Review and publish
|
|
|
|
### Predictive Resolution
|
|
|
|
- AI predicts likely resolution before tree starts
|
|
- "Based on the description, this is probably X (85% confidence)"
|
|
- Option to jump to likely solution
|
|
|
|
### Import from Text/Documentation
|
|
|
|
- Paste existing runbook or documentation
|
|
- AI parses and creates tree structure
|
|
- Review and refine
|
|
|
|
---
|
|
|
|
## Parking Lot - Quick Ideas
|
|
|
|
*Quick-capture ideas to evaluate later:*
|
|
|
|
- [ ] Browser extension to capture screenshots into sessions
|
|
- [ ] QR codes on physical equipment linking to relevant trees
|
|
- [ ] Customer-facing trees (end-user self-service)
|
|
- [ ] Tree templates for common scenarios
|
|
- [ ] Scheduled tree reminders (monthly server maintenance checklist)
|
|
- [ ] Integration with monitoring tools (trigger tree from alert)
|
|
- [ ] Multi-language tree support
|
|
- [ ] Conditional logic based on time of day / day of week
|
|
- [ ] SLA timers visible during session
|
|
- [ ] Escalation workflows with approval chains
|
|
- [ ] Custom note formatting templates for different ticket systems
|
|
- [ ] "Options on the go" - select pre-made steps mid-tree and jump to relevant point
|
|
- [ ] Import plan function - write in text format and import as tree
|
|
|
|
---
|
|
|
|
## Long-Term Vision (Year 2+)
|
|
|
|
### Product Evolution
|
|
|
|
- Self-learning system (trees improve automatically based on usage)
|
|
- Voice-guided troubleshooting (hands-free operation)
|
|
- AR/VR support (on-site equipment identification)
|
|
- AI co-pilot (real-time suggestions during troubleshooting)
|
|
|
|
### Market Expansion
|
|
|
|
- Vertical-specific tree libraries (healthcare IT, financial services, education)
|
|
- Certification program for tree authors
|
|
- Professional services (custom tree development)
|
|
- Training and consultation services
|
|
|
|
### Platform Maturity
|
|
|
|
- 99.9% uptime SLA
|
|
- Global CDN deployment
|
|
- Advanced compliance (SOC 2, ISO 27001)
|
|
- Enterprise support tiers
|
|
- White-glove onboarding
|
|
|
|
---
|
|
|
|
## Idea Evaluation Criteria
|
|
|
|
When evaluating which ideas to pursue:
|
|
|
|
| Criteria | Weight | Questions |
|
|
|----------|--------|-----------|
|
|
| User demand | High | Are users asking for this? |
|
|
| Revenue impact | High | Will this drive upgrades or reduce churn? |
|
|
| Differentiation | Medium | Does this set us apart from alternatives? |
|
|
| Development effort | Medium | How long to build MVP? |
|
|
| Maintenance burden | Medium | Ongoing cost to support? |
|
|
| Strategic fit | Medium | Does this align with our vision? |
|
|
|
|
---
|
|
|
|
## How to Add Ideas
|
|
|
|
When adding new ideas to this document:
|
|
|
|
1. **Describe the concept** - What is it? Why would users want it?
|
|
2. **Provide an example** - Concrete scenario showing the feature in action
|
|
3. **Note technical considerations** - What would need to change?
|
|
4. **Estimate complexity** - Simple / Medium / Complex
|
|
5. **Identify dependencies** - What needs to exist first?
|
|
|
|
---
|
|
|
|
*This is a living document. Add ideas freely, evaluate periodically, and move promising concepts to GitHub Issues when ready to implement.*
|