Changing ourselves is rarely easy. We think about our looks, habits, lifestyle, social circle, or screen time. However, we often avoid the harder question: how do we really make change happen? As requirements engineers, we also face change in projects, teams, and stakeholder work. Therefore, I explore how to change as a engineer and become the person I want to be.
The Safety of Familiarity
Staying the same feels safe. It’s like sticking to the known path where we can predict the hurdles. Change, on the other hand, brings uncertainty. Sure, sticking to what we know shields us, but it can also hold us back. Do we really know what’s best for us? What if we don’t change? Is the risk of change worth it? And are we alone in wanting to change?
Navigating Through Rules
Rules shape our actions and boundaries. They tell us what’s allowed and what’s not. Whether it’s legal statutes or personal values, rules guide us. But finding the right balance is crucial.
The Extremes of Control
Some of us thrive on structure, planning every detail of our lives. Others prefer to go with the flow, living in the moment without much thought for the future. But neither extreme leads to lasting happiness.
Crafting Your Path
Creating our own rules can be a game-changer. It’s the first step towards improving our lives.
Three Simple Steps
Three simple steps unlock your change as a requirements engineer:
- Identify Your Goals: What do you want to change or achieve? Start with one thing at a time.
- Spot the Roadblocks: What’s holding you back? It could be internal barriers like procrastination or external ones like a demanding job.
- Define Your Rules: What actions will you take? Set clear guidelines for yourself.
Making It Real
Let’s say you want to exercise more. You acknowledge your tendency to procrastinate and your busy schedule. So, you decide to schedule a fixed workout time each week and squeeze in short home exercises daily.
Embracing Change
Setting rules is just the beginning for unlocking change as a requirements engineer. The real challenge lies in sticking to them. Change starts with action. If we don’t take that first step, nothing will ever change.
What’s Next?!
Understanding how to embrace change as an engineer is only the beginning. The next challenge lies in applying that mindset to real-world software projects. Gathering the right requirements, managing expectations, and overcoming technical complexity demand both skill and adaptability. Ready to discover how to get exactly what’s needed to succeed in demanding projects? Continue your journey with Getting What We Need for Challenging Software Development (opens in a new tab).
What’s Next?
Change starts with a clear decision. However, lasting change needs more than good intentions. I need simple rules that guide my behavior, protect my focus, and help me act when motivation fades.
Therefore, I continue with How to Set Rules for Personal Change as Requirements Engineer. In the next article, I show how clear personal rules help me turn change into structure. As a result, I can grow with more direction and become a more reliable requirements engineer.
Strengthen Your Personal Growth
Read Personal Growth to see how I connect self-understanding, change, habits, discipline, decisions, stress, personality, cognition, and openness in one practical overview. This main article also shows how personal growth strengthens stakeholder management, elicitation, body language, presentation, storytelling, repartee, negotiation, and effective communication. Therefore, I can grow as a person and become more effective as a requirements engineer.
Credits: Photo by Gerd Altmann from Pexels