It is a very broad question. It depends on your field, nature of the projects, complexity, purpose of exchange and ... .
...
1 reply by Erick Rene Sanchez Campos
Sep 29, 2026 3:33 AM
Erick Rene Sanchez Campos
...
Dear Abolfazl,
This question is based on our certificate discussion about the Prompt Engineering Exchange. While prompt engineering is a fundamental AI skill applicable to any field, our Project Management for Engineering certificate specifically focus on structured outputs. Thank you for your comment.
Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
Excellent reference source, Sergio, thank you for sharing.
Saving Changes...
Imran AfzalAuthor| The Strategic PMOCary, NC, United States
One thing I’ve noticed with prompt engineering discussions is that teams often focus heavily on the prompts themselves while underestimating the surrounding operating system.
In practice, the most effective “Prompt Engineering Exchanges” I’ve seen are less about discovering a magic prompt and more about creating repeatable patterns for experimentation, evaluation, and knowledge sharing.
A few areas I think matter most:
• Structured prompt libraries tied to real business use cases rather than isolated examples • Shared evaluation criteria (accuracy, clarity, hallucination risk, decision usefulness, time savings, etc.) • Comparison across models and prompting strategies instead of assuming one approach generalizes everywhere • Human-in-the-loop review processes for sensitive or high-impact outputs • Lightweight governance around data privacy, intellectual property, and organizational standards
On the technique side, I’ve generally seen the most value from:
• role/context framing • decomposition of complex tasks into smaller reasoning steps • iterative refinement • retrieval-based approaches grounded in organizational knowledge • and standardized templates for recurring workflows
The biggest shift, in my opinion, is that prompt engineering is gradually becoming less of an individual skill and more of an organizational capability.
The organizations getting the most value from AI usually are not the ones with the “best prompts.” They are the ones building systems that help teams consistently generate, evaluate, share, and improve AI-assisted work over time.
...
1 reply by Erick Rene Sanchez Campos
Sep 29, 2026 3:44 AM
Erick Rene Sanchez Campos
...
Outstanding discussion Imran. I strongly agree with your point that evaluation is an important part of any Prompt Engineering Exchange. Teams should not only share prompts, but also discuss the quality of the output based on factors such as accuracy, clarity, usefulness, risk of hallucination, time saved, and relevance to the business situation." This is specially critical in the engineering team, where even minor hallucination or inaccuracies can compromise design integrity, violate safety standards, or lead to cost errors during the project life cycle.
Saving Changes...
Deepak MalhotraLeader - Customer Success| CiscoHyderabad, Telangana, India
A Prompt Engineering Exchange should ideally go beyond simply collecting good prompts. In my view, the real value comes from creating a structured space where professionals can test, evaluate, improve, and reuse prompts for practical business and project management use cases.
The most useful tools would include approved generative AI platforms such as ChatGPT, Microsoft Copilot, Gemini, Claude, or other enterprise AI tools. Along with these, shared prompt libraries, reusable templates, knowledge repositories, collaboration platforms, and version control can help teams capture what worked, what did not work, and how prompts can be improved over time.
The models best suited for this type of exchange are large language models that can understand context, summarize information, generate structured responses, support analysis, and assist with decision-making. In project management, this can be useful for risk identification, stakeholder communication, meeting summaries, project documentation, lessons learned, status reporting, and decision support. However, the choice of model should also depend on data privacy, security, compliance, and organizational standards. The techniques should be practical, repeatable, and easy for teams to apply. Some of the most useful techniques include role and context framing, clear task instructions, breaking complex work into smaller steps, asking for structured outputs, using examples, refining prompts based on the response, and validating the output before using it. For recurring workflows, standardized templates and checklists can help improve consistency.
I also feel that evaluation is an important part of any Prompt Engineering Exchange. Teams should not only share prompts, but also discuss the quality of the output based on factors such as accuracy, clarity, usefulness, risk of hallucination, time saved, and relevance to the business situation.
Most importantly, a Prompt Engineering Exchange should encourage responsible use of AI. AI can support project managers with speed, structure, and new perspectives, but human judgment, ethics, confidentiality, and accountability should remain central. The goal should not be to find one perfect prompt, but to build a practical capability that helps teams consistently improve AI-assisted work over time.
...
1 reply by Erick Rene Sanchez Campos
Sep 29, 2026 4:26 AM
Erick Rene Sanchez Campos
...
Excellent discussion Deepak, it makes me think about future prompt improvements to adapt dynamically alongside the tools, new data, and probably new GenAI.
I really like how you listed the approved most common generative AI platforms. I also agree that shared prompt libraries, repositories, reusable templates, collaboration platforms, and version control can help teams capture what worked.
However, looking at how prompts improve over time, when you mentioned "what did not work how prompts can be improved over time." I think there is an interesting area of opportunity to explore. Because the prompt you use with AI today will likely yield different results in the future since the models are constantly changing and updated with new data, algorithms, and capabilities. So maybe improving and updating prompts over time is not a bad idea. I do it all the time with my team. What are you thoughts on this?
It is a very broad question. It depends on your field, nature of the projects, complexity, purpose of exchange and ... .
Dear Abolfazl,
This question is based on our certificate discussion about the Prompt Engineering Exchange. While prompt engineering is a fundamental AI skill applicable to any field, our Project Management for Engineering certificate specifically focus on structured outputs. Thank you for your comment. Saving Changes...
One thing I’ve noticed with prompt engineering discussions is that teams often focus heavily on the prompts themselves while underestimating the surrounding operating system.
In practice, the most effective “Prompt Engineering Exchanges” I’ve seen are less about discovering a magic prompt and more about creating repeatable patterns for experimentation, evaluation, and knowledge sharing.
A few areas I think matter most:
• Structured prompt libraries tied to real business use cases rather than isolated examples • Shared evaluation criteria (accuracy, clarity, hallucination risk, decision usefulness, time savings, etc.) • Comparison across models and prompting strategies instead of assuming one approach generalizes everywhere • Human-in-the-loop review processes for sensitive or high-impact outputs • Lightweight governance around data privacy, intellectual property, and organizational standards
On the technique side, I’ve generally seen the most value from:
• role/context framing • decomposition of complex tasks into smaller reasoning steps • iterative refinement • retrieval-based approaches grounded in organizational knowledge • and standardized templates for recurring workflows
The biggest shift, in my opinion, is that prompt engineering is gradually becoming less of an individual skill and more of an organizational capability.
The organizations getting the most value from AI usually are not the ones with the “best prompts.” They are the ones building systems that help teams consistently generate, evaluate, share, and improve AI-assisted work over time.
Outstanding discussion Imran. I strongly agree with your point that evaluation is an important part of any Prompt Engineering Exchange. Teams should not only share prompts, but also discuss the quality of the output based on factors such as accuracy, clarity, usefulness, risk of hallucination, time saved, and relevance to the business situation." This is specially critical in the engineering team, where even minor hallucination or inaccuracies can compromise design integrity, violate safety standards, or lead to cost errors during the project life cycle. Saving Changes...
A Prompt Engineering Exchange should ideally go beyond simply collecting good prompts. In my view, the real value comes from creating a structured space where professionals can test, evaluate, improve, and reuse prompts for practical business and project management use cases.
The most useful tools would include approved generative AI platforms such as ChatGPT, Microsoft Copilot, Gemini, Claude, or other enterprise AI tools. Along with these, shared prompt libraries, reusable templates, knowledge repositories, collaboration platforms, and version control can help teams capture what worked, what did not work, and how prompts can be improved over time.
The models best suited for this type of exchange are large language models that can understand context, summarize information, generate structured responses, support analysis, and assist with decision-making. In project management, this can be useful for risk identification, stakeholder communication, meeting summaries, project documentation, lessons learned, status reporting, and decision support. However, the choice of model should also depend on data privacy, security, compliance, and organizational standards. The techniques should be practical, repeatable, and easy for teams to apply. Some of the most useful techniques include role and context framing, clear task instructions, breaking complex work into smaller steps, asking for structured outputs, using examples, refining prompts based on the response, and validating the output before using it. For recurring workflows, standardized templates and checklists can help improve consistency.
I also feel that evaluation is an important part of any Prompt Engineering Exchange. Teams should not only share prompts, but also discuss the quality of the output based on factors such as accuracy, clarity, usefulness, risk of hallucination, time saved, and relevance to the business situation.
Most importantly, a Prompt Engineering Exchange should encourage responsible use of AI. AI can support project managers with speed, structure, and new perspectives, but human judgment, ethics, confidentiality, and accountability should remain central. The goal should not be to find one perfect prompt, but to build a practical capability that helps teams consistently improve AI-assisted work over time.
Excellent discussion Deepak, it makes me think about future prompt improvements to adapt dynamically alongside the tools, new data, and probably new GenAI.
I really like how you listed the approved most common generative AI platforms. I also agree that shared prompt libraries, repositories, reusable templates, collaboration platforms, and version control can help teams capture what worked.
However, looking at how prompts improve over time, when you mentioned "what did not work how prompts can be improved over time." I think there is an interesting area of opportunity to explore. Because the prompt you use with AI today will likely yield different results in the future since the models are constantly changing and updated with new data, algorithms, and capabilities. So maybe improving and updating prompts over time is not a bad idea. I do it all the time with my team. What are you thoughts on this? Saving Changes...
