Program Manager| HARPER SRLSanto Domingo / Distrito Nacional, Dominican Republic
keeping it small and tied to a real pain point. Start with one clear problem the team feels (not something abstract), test a simple improvement, and measure if it actually made things easier or faster. If it works, then scale it. Also, involve the team early. If they see the value, adoption happens naturally. If not, even good ideas fail. For monthly improvements, consistency matters more; dmall changes that stick usually create more impact than big initiatives that fade.
...
1 reply by Francisco Herrera
Mar 31, 2026 12:54 PM
Francisco Herrera
...
Thanks for the advice Lissette! It's wotrh it try it, Regards! Francisco.
Program Manager, PPM&PMO Specialist.| Coppel, Mexico.Culiacán, Sinaloa, Mexico
Mar 30, 2026 7:47 PM
Replying to Lissette Indhira Pimentel Sosa
...
keeping it small and tied to a real pain point. Start with one clear problem the team feels (not something abstract), test a simple improvement, and measure if it actually made things easier or faster. If it works, then scale it. Also, involve the team early. If they see the value, adoption happens naturally. If not, even good ideas fail. For monthly improvements, consistency matters more; dmall changes that stick usually create more impact than big initiatives that fade.
Thanks for the advice Lissette! It's wotrh it try it, Regards! Francisco. Saving Changes...
Start small, pick one problem, test a simple idea, and measure results before scaling. Use AI tools like Google Gemini for quick insights, track progress monthly, and keep improving based on real feedback.
...
1 reply by Francisco Herrera
Apr 15, 2026 12:19 PM
Francisco Herrera
...
Thanks Syed Ashir Riaz for the feedback of using the KISS methodology (Keep It Short and Simple).
Sstarting small by picking one specific problem and testing a simple idea is the most effective way to avoid overcomplicating the process and incorporating AI tools like Google Gemini will be a game-changer for getting quick insights and staying efficient.
Keep visible and repeat regularly the objective of the improvement (What) and the project timeline (When)
Having key criteria of the improvement and publish monthly the improved value (Characterization of the improvement + Useful for strategy to test idea and value over cost)
Provide summary of activities and results on monthly basis
Provide users or stakeholders feedback regularly to check early adoption and/or mitigation
Recognize team effort or give visibility to team/team member
...
1 reply by Francisco Herrera
Apr 16, 2026 3:14 PM
Francisco Herrera
...
Thanks for these points! I especially like the idea of regularly repeating the objective and timeline; sometimes the team loses focus on the 'Why' during execution.
Program Manager, PPM&PMO Specialist.| Coppel, Mexico.Culiacán, Sinaloa, Mexico
Apr 01, 2026 2:06 AM
Replying to Syed Ashir Riaz
...
Start small, pick one problem, test a simple idea, and measure results before scaling. Use AI tools like Google Gemini for quick insights, track progress monthly, and keep improving based on real feedback.
Thanks Syed Ashir Riaz for the feedback of using the KISS methodology (Keep It Short and Simple).
Sstarting small by picking one specific problem and testing a simple idea is the most effective way to avoid overcomplicating the process and incorporating AI tools like Google Gemini will be a game-changer for getting quick insights and staying efficient.
Program Manager, PPM&PMO Specialist.| Coppel, Mexico.Culiacán, Sinaloa, Mexico
Apr 01, 2026 5:54 AM
Replying to Gwenola Michaud
...
Keep visible and repeat regularly the objective of the improvement (What) and the project timeline (When)
Having key criteria of the improvement and publish monthly the improved value (Characterization of the improvement + Useful for strategy to test idea and value over cost)
Provide summary of activities and results on monthly basis
Provide users or stakeholders feedback regularly to check early adoption and/or mitigation
Recognize team effort or give visibility to team/team member
Thanks for these points! I especially like the idea of regularly repeating the objective and timeline; sometimes the team loses focus on the 'Why' during execution.