<aside>
</aside>
<aside>
🪄 Products
</aside>
<aside>
</aside>
<aside>
I've always been bored with the routine that so many people easily come to terms with... I wanted to make an impact and define myself as a problem solver with no limitations was the way to cure this boredom. Now that I've looked closer at the mainstream ecosystem, I realize that's what they call a product manager there.
</aside>
Main Challenges
Results and Impacts
Approach and Main Actions
Lessons Learned
I've never stuck to one branch. The most common thing I've heard about myself is always the same: she's constantly jumping from one branch to another.
In school, the only place I wasn't was in class: if excuses for theater, choir, and wall newspapers didn't work anymore, I'd dump out the library books for the umpteenth time that year and weave a new order for them, getting busy organizing. In university, my only joy was that architecture, and later project management, officially meant jumping between branches was my duty, not something I needed to make excuses for. Of course, from my perspective, I'm not sure everyone shares this view, but I was happy with it.
I was about to write the reason for my constant jumping as "I'm fascinated by problems and..." but to be honest, more than that, I can't ignore a problem I see in my circle of attention, so I'm compelled to solve it, but nothing can deny the pleasure when the solution comes to life right in front of you.
After finishing my studies, I officially introduced myself as a problem solver and started designing diverse solutions for the daily issues I was dealing with, and worked to bring them to fruition. A few examples are examined in this portfolio, and although, given the conditions and context they were raised in, they haven't reached the fruition they should yet, they're not sterile, and I'm optimistic about their blossoming :)
All this time, sometimes I was an architect, mostly a project manager, and always a problem solver, and along the way I designed, analyzed, sometimes coded, and always created stories. Now that I'm a bit closer to the mainstream ecosystem, while exploring different paths and measuring their freedom for jumping between branches, encountering product management lit the light I needed, so this is the aspect the ecosystem should see from me: Hannah as a PM.
When I first decided to take steps to enter the ecosystem, the issue I faced was having scattered skills that I couldn't find a specific place for to achieve the maximum impact I had in mind. I knew what I was capable of, what skills I had, and how competent I was, but I didn't know who I was officially, so I had to find my official title.
In my first encounter with available positions, a broad field was in front of me where I could use a part of my skills in each one. With the business-building background I had, I was reasonably familiar with each part of the process and could respond to JD requirements with that familiarity. I had mentioned the scattering of skills earlier, and if I want to expand it a bit, I should say the positions I could apply for ranged from financial and administrative to creativity and diverse project management, but the positions I wanted to apply for were those that would make my unofficial problem solver official. I examined a number of opportunities that were somewhat close to this title, and for each one, I had to select a part of my assets and present them, which didn't seem right. During the examination of different positions and getting closer to the ecosystem space, I came to the conclusion that product management has the most affinity with what I have been so far. This conclusion gained strength by returning to past experiences and looking at them again, this time as products.
<aside>
Hannah Rahimii :)
Lifestyle: Curious, self-driven, multidisciplinary
Mindset: Seeks impact, clarity, and legitimacy within the mainstream ecosystem
Goals
Pain Points
Behaviors
Needs
How PM Fits </aside>
About Hannah