Educational perspective · Revised September 25, 2026. This article does not report findings from Dr. A Ashour’s doctoral study.
When planning an AI initiative, include time and ownership for learning, review, and ongoing adjustment.
Budget for more than access
Include practice time, review effort, documentation, and help with exceptions in the proposed plan. Identify who owns each part. Software access alone does not demonstrate that a team can use it appropriately.
Choose a small pilot
Select a limited task with clear source information and an observable output. Define the review standard before beginning. Keep a record of corrections and unresolved questions so the next decision has evidence behind it.
Listen before expanding
Ask the people doing the work what became easier and what became harder. Compare their feedback with the pilot records. Check whether the process moved effort to another person or created a new review burden.
Make a deliberate decision
At the end of the pilot, choose whether to expand, revise, or pause. Record why. A useful decision considers the quality of the result, total effort, responsibilities, and unresolved risks. These are planning suggestions, not claims about the outcomes of Dr. A Ashour’s doctoral study.
Further reading
For an external risk management reference, see NIST’s AI Risk Management Framework. The practical prompts above are editorial suggestions, not NIST certification or research findings.
