Frequently Asked Questions

No. Expert-Driven Development is built on the premise that domain expertise is the prerequisite, not coding ability. You are the subject matter expert in your workflow. The AI generates the code; your job is to define the problem clearly, test the output, and iterate until the tool works correctly.

The EDD methodology teaches you how to communicate effectively with AI tools so that your expertise drives the solution. Many successful EDD tools have been built by Marines with zero prior programming experience.

M365 Copilot is the preferred tool for DoW environments because it operates within the Microsoft security boundary and is approved for use with CUI-adjacent (but not classified) data. Azure OpenAI is also approved for organizational use.

Other tools may be used if they are approved by your command's cybersecurity and information assurance office. The key requirement is that the tool must be authorized for use on your network and with your data classification level.

This is expected and normal. AI tools do not produce perfect output on the first attempt. The EDD methodology uses an iteration loop that accounts for this:

1. Be specific about what is wrong. Instead of saying "this doesn't work," describe exactly what happened versus what you expected. For example: "The filter on the gallery shows all items instead of only items where Status equals 'Active'."
2. Provide the error context. Copy and paste any error messages directly into your next prompt. Include the exact formula or code that failed.
3. Break the request into smaller pieces. If a complex prompt produces broken output, split it into sequential steps. Ask for one function at a time, verify it works, then move to the next.
4. Try a different approach. If three iterations on the same approach are not converging, describe your goal from a different angle or ask the AI to suggest alternative methods.

The typical build involves 50-150 prompt iterations. Each wrong answer is an opportunity to refine your requirements.

Based on data from EDD training cohorts:

The first tool takes longer because you are simultaneously learning the methodology, the AI interaction patterns, and the Power Platform. Subsequent tools benefit from your accumulated prompt library, template familiarity, and platform knowledge.

EDD tools are built on unclassified platforms (Power Platform, SharePoint Online) and are designed for unclassified workflows. If your use case involves classified data:

• The tool itself must reside on an appropriately classified network
• AI-assisted development prompts must be written using only unclassified descriptions of the workflow
• No classified data, system names, or network architecture details should appear in any AI prompt
• Consult your SSO (Special Security Officer) or Information Assurance Manager before proceeding

Yes. The EDD SOP requires supervisor approval at the planning phase. Specifically:

• The Problem Definition Worksheet includes a mandatory supervisor signature block
• This document must be signed before development begins
• The supervisor's approval confirms that the problem is worth solving, the approach is reasonable, and the developer has authorization to spend time on the project

This is not bureaucratic overhead; it ensures alignment between the developer's effort and the command's priorities, and it provides top-cover for the time invested in building the tool.

The EDD methodology is platform-agnostic in principle, but the training and SOP focus on the Microsoft Power Platform because it is the most widely available and approved toolset in DoW environments:

• Power Apps — Build canvas apps and model-driven apps for data entry, tracking, and workflow tools
• Power Automate — Create automated workflows, approval processes, and scheduled tasks
• Power BI — Build dashboards, reports, and data visualizations
• SharePoint — Use as a data backend (lists), document storage, and collaboration platform

These tools are included in most DoW M365 licenses and do not require separate procurement or ATO (Authority to Operate) processes in most cases.

If your tool collects, stores, displays, or processes Personally Identifiable Information (PII), you must take additional steps:

1. Document it in the Data Considerations section of the Problem Definition Worksheet
2. Complete a PIA (Privacy Impact Assessment) Threshold Analysis to determine whether a full PIA is required
3. Coordinate with your Privacy Officer or the installation Privacy Act coordinator
4. Implement required controls:
   • Access restricted to authorized users only
   • Data encrypted at rest and in transit (SharePoint/Power Platform handles this by default)
   • Audit logging enabled
   • Data retention and disposal policy defined
5. Document all controls in the QA Review Checklist compliance section

Do not skip this process. PII handling violations carry serious consequences.

Most DoW personnel with M365 accounts already have Power Platform access. To check:

1. Navigate to make.powerapps.com and sign in with your DoW email
2. If you can access the Power Apps maker portal, you have a license
3. If access is denied, contact your S-6 / G-6 / IT support office to request a Power Apps license assignment

Common license types that include Power Platform access:

• Microsoft 365 E3 or E5 (includes basic Power Apps and Power Automate)
• Power Apps per-user plan (for premium connectors)
• Power Automate per-user plan (for premium flow features)

Yes, and this is encouraged. One of the core principles of EDD is that well-documented tools can be replicated and adapted by other organizations. To share your tool effectively:

1. Register it in the Tool Registry so others can discover it
2. Complete the documentation package, especially the Replication Guide and Adaptation Guide, which are specifically designed to enable other units to rebuild or customize your tool
3. Share the documentation through your organization's knowledge management channels, or contribute it to the EDD GitHub repository
4. Consider presenting your tool at a Marine Coders meetup or similar community of practice forum

The Adaptation Guide template is specifically designed to help another unit take your tool and modify it for their environment, data sources, and branding without starting from scratch.