When setting up DevOps pipelines, there are several possibilities to implement all of the automation for builds and deployments. One of the most effective ways to increase efficiency and consistency is to reuse pipeline components such as steps, jobs, and stages across different projects. This approach helps teams avoid duplication, enforce standards, and simplify maintenance. But not everything in a pipeline can be fully standardized, so some parts will always need to be customized for specific applications or environments. We have created a complete flow for pipeline reuse where we combined YAML templates, shared jobs and stages, and pipeline templates to provide a consistent CI/CD structure across projects. In this session I will share some of the insights about how we have set up reusable components, where we applied templates, and what we kept project‑specific. Next to the flow, we will also give insights on some issues we have encountered, and some things you need to be aware of when using this setup. This setup has given us clear benefits: faster onboarding of new teams, reduced duplication of effort, and more reliable pipelines thanks to centralized, proven patterns. At the same time, we learned that governance and documentation are critical to prevent confusion and unintended changes.