<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Ioana Ognibeni (Marinescu) on Medium]]></title>
        <description><![CDATA[Stories by Ioana Ognibeni (Marinescu) on Medium]]></description>
        <link>https://medium.com/@ioanaa.cristinaa?source=rss-6d4cac561a1c------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*8xcfoMJvGTl1MDg_fk-j9Q.jpeg</url>
            <title>Stories by Ioana Ognibeni (Marinescu) on Medium</title>
            <link>https://medium.com/@ioanaa.cristinaa?source=rss-6d4cac561a1c------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 11:50:43 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ioanaa.cristinaa/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Don’t Run Behind Competitors. Run to Meet Your Customers.]]></title>
            <link>https://medium.com/@ioanaa.cristinaa/title-dont-run-behind-competitors-run-to-meet-your-customers-ccbe36759e8e?source=rss-6d4cac561a1c------2</link>
            <guid isPermaLink="false">https://medium.com/p/ccbe36759e8e</guid>
            <dc:creator><![CDATA[Ioana Ognibeni (Marinescu)]]></dc:creator>
            <pubDate>Sun, 08 Mar 2026 21:07:20 GMT</pubDate>
            <atom:updated>2026-03-08T21:07:35.924Z</atom:updated>
            <content:encoded><![CDATA[<p>Why AI-powered speed will make the copycat trap even more dangerous</p><p>AI is about to make shipping features faster than ever, and I think that’s going to make an old problem significantly worse: <strong>the temptation to just copy what competitors have</strong>. When building features takes less time and effort, the default instinct to look sideways instead of looking at your customers will only get stronger.</p><p>I’ve lived this firsthand, years ago, in a product organization where our entire focus revolved around <strong><em>killing the competition at all costs.</em></strong> What happened was not dramatic or sudden — it was a slow erosion of everything important in the product flow:</p><ul><li>We lost track of our own ideal customer profile, which was slightly different from our competitor’s but different enough to matter.</li><li>Because we were mirroring their moves, we ended up solving for problems we hadn’t taken the time to understand first — we skipped the problem space entirely and went straight to building whatever they had built.</li><li>Our team got progressively more demotivated, because it turns out that permanently running behind a younger, more agile competitor with less legacy than you is an incredibly draining way to spend your energy.</li><li>We accumulated tech debt for no good reason, bolting on features that didn’t fit our architecture because they fit someone else’s.</li><li>And at some point, nobody on the team — including me — could clearly articulate what our strategy was, or why we were doing what we were doing.</li></ul><p><strong>What we should have done instead was look at our customers’ actual needs, desires and jobs to be done. </strong>We should have understood the market direction, mapped our competitive alternatives honestly so we knew where we stand, taken a hard look at our own product and organizational strengths and weaknesses, and then come up with a series of winning bets we could have actually tested and validated.</p><blockquote>That’s the difference between strategy and reaction. Knowing what your competitor does is awareness, and awareness is valuable.</blockquote><blockquote>But building your roadmap as a response to theirs is not a strategy — it’s a lazy plan dressed up as urgency.</blockquote><p>With AI making it easier to ship fast, the companies that win won’t be the ones who copy fastest.</p><p>They’ll be the ones who took the time to understand what’s actually worth building.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ccbe36759e8e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[I Couldn’t Find a Place to Practice AI Evals, So I Built One]]></title>
            <link>https://medium.com/@ioanaa.cristinaa/i-couldnt-find-a-place-to-practice-ai-evals-so-i-built-one-3bdbd48d01dd?source=rss-6d4cac561a1c------2</link>
            <guid isPermaLink="false">https://medium.com/p/3bdbd48d01dd</guid>
            <dc:creator><![CDATA[Ioana Ognibeni (Marinescu)]]></dc:creator>
            <pubDate>Sun, 08 Mar 2026 19:06:13 GMT</pubDate>
            <atom:updated>2026-03-08T19:06:13.173Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>What a Product Manager learns by shipping an AI feature with ‘bare hands’</strong></p><p>I wanted to get better at AI evaluations — not in theory, because I’ve read enough papers and blog posts, but in practice. Actually judging outputs, spotting hallucinations, figuring out what “good enough” means when there’s no objectively right answer. The problem was that I couldn’t find a sandbox for that. Every resource I found was either too academic or too technical, and none of them let me actually <em>do</em> the work. So I built one myself, and made it available to everyone who wants to give it a try.</p><h4><strong>What’s</strong> <strong>in</strong> <strong>it</strong></h4><p>The app, <a href="https://ai-quality-lab.replit.app/">AI Quality Lab</a>, covers three things:</p><ul><li>First, basic theory for non-technical PMs. Not a deep learning course, just enough to understand what you’re evaluating and why it matters.</li><li>Second, practice exercises across 11 quality dimensions, with 3 challenges each, plus 6 complex scenarios that use LLM-as-a-judge — you submit your evaluation, Claude assesses how well you did, and you need to bring your own API key (everything stays in the browser except the API call itself).</li><li>Third, 25 real traces for hands-on error analysis, without any LLM involvement — you read the trace, identify what went wrong, and compare your analysis with an expert answer. This last part turned out to be the most useful one, because it’s the closest to what you’d actually do on the job.</li></ul><h4><strong>What</strong> <strong>I</strong> <strong>actually</strong> <strong>learned</strong> <strong>by</strong> <strong>building</strong> <strong>it</strong></h4><p>The original plan was straightforward: build a learning app, use an LLM to judge answers, ship it.</p><p>Here’s what actually happened:</p><ul><li>Claude Haiku started hallucinating, and not in the way you’d expect. It wasn’t giving wrong answers to real questions — it was judging user answers that were never written. It would fabricate what the user supposedly said, then evaluate its own fabrication with full confidence. Creative, but deeply weird. Haiku also turned out to be noticeably less reliable at producing well-formed JSON compared to Sonnet, which matters a lot when your entire feedback loop depends on structured output.</li><li>Then Claude helpfully added a deprecated 2024 API model to my specs, which I only caught when the whole thing broke in production. Debugging an error that was caused by your own AI assistant recommending outdated code is a very specific kind of frustration that I hadn’t anticipated.</li><li>Somewhere along the way, I also realized that using an LLM for everything is unnecessary and often counterproductive. For basic garbage detection — did the user actually write something meaningful? — a few lines of code work better, faster, and for free. Same for synonym matching or calculating a numerical score. An LLM is overkill when the task has a deterministic answer.</li><li>Oh, and Replit turned out to be more expensive than it looks — this app cost about €90 in credits.</li></ul><h4><strong>Where</strong> <strong>I</strong> <strong>landed</strong></h4><p>The architecture I ended up with is the one I’d now recommend to anyone building an AI feature, and it’s basically three layers of checks for what should have been a single step.</p><p>Before the LLM call, I run deterministic checks:</p><ul><li>is this input garbage?</li><li>does it match a known synonym?</li><li>can we score this without calling an API at all?</li></ul><p>The LLM itself only handles what code genuinely can’t do: semantic judgment about whether an evaluation shows real understanding and sound reasoning. And after the LLM responds, I verify: did the model hallucinate? Did it reference something the user never said? Is the JSON actually valid?</p><p>It’s not elegant, but it works reliably.</p><h4><strong>The</strong> <strong>real</strong> <strong>takeaway</strong></h4><blockquote><strong>Shipping an AI feature feels like trying to catch a fish with bare hands </strong>— there’s always an angle you didn’t consider, and every round of testing surfaces something new in a place you weren’t looking.</blockquote><blockquote>If you’re a PM who hasn’t built anything with AI yet, I’d genuinely recommend investing €70–90 in a vibe coding setup and making something, anything. The experience of debugging a hallucinating model changes forever how you think about AI features.</blockquote><p>The app is still an early version and I keep building on it, if it’s valuable. If it’s useful to you too, let me know — that’s what decides whether it grows. Feel free to reach out to me on <a href="https://www.linkedin.com/in/ioanamarinescu/">LinkedIn</a>.</p><p>AI Quality lab: <a href="https://ai-quality-lab.replit.app/">https://ai-quality-lab.replit.app</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3bdbd48d01dd" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to create a culture of ownership]]></title>
            <link>https://medium.com/@ioanaa.cristinaa/how-to-create-a-culture-of-ownership-aa0ffd6ab431?source=rss-6d4cac561a1c------2</link>
            <guid isPermaLink="false">https://medium.com/p/aa0ffd6ab431</guid>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[ownership]]></category>
            <category><![CDATA[culture-change]]></category>
            <dc:creator><![CDATA[Ioana Ognibeni (Marinescu)]]></dc:creator>
            <pubDate>Mon, 23 Oct 2023 16:25:30 GMT</pubDate>
            <atom:updated>2023-10-23T16:26:49.881Z</atom:updated>
            <content:encoded><![CDATA[<h4>10 concrete steps for leaders and business owners</h4><h3>I. Why “Ownership”</h3><p>Have you ever felt the need to ‘clone’ yourself? This is probably the best way to achieve that: create a culture of ownership and enable your team members to come to work with purpose and drive.</p><p>As much as ownership is important in any organization, in a startup, it is vital. You need your team members to feel invested in the success of the company and motivated to give their absolute best.</p><p>When people own their work, end to end, there are no loose ends, there is no bystander effect, and things do not fall between the cracks. Ultimately, the results are shown in the business metrics.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*cKeBjR9flcfd-mUn" /><figcaption>Photo by <a href="https://unsplash.com/@claybanks?utm_source=medium&amp;utm_medium=referral">Clay Banks</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>II. How to create a culture of ownership</h3><h4>1- Look with honesty at what is currently not working</h4><p>When working to improve team members’ sense of ownership, one has to consider 2 sides:</p><ul><li><strong>Giving responsibility and trusting the other one with the outcome</strong></li></ul><p>If you have the right people with the right mindset, ready to take on responsibility and get things done, but you are reluctant to give them trust, conflicts will arise, and eventually, these people will either give up or leave.</p><blockquote><em>One cannot really feel responsible for something one cannot directly impact. Micromanagement is the ownership’s biggest enemy.</em></blockquote><p>Are leaders in your company leading with context or control? Are they giving end-to-end responsibility to their team members and trusting them with the outcome, or constantly interfering in their daily work, correcting their actions even in small regards, and changing direction without letting them know?</p><ul><li><strong>Taking responsibility and doing one’s best to deliver the outcomes</strong></li></ul><p>When people feel they own something, they hold themselves, each other, and even their leaders responsible for making that come true.</p><p>Observable behaviors are:</p><ul><li>Taking initiative without being explicitly asked: <em>“I can take that with me”, “I will do that!”</em></li><li>Having a sense of urgency and focus — <em>“We need to get this done by…”, “How is this going to help us reach our goal?”</em></li><li>Have a pragmatic approach — <em>“We need to first prototype this and test it with users”, “That is a minor bug which happens only in a rare edge case — we are not investing energy in this.”</em></li><li>Keeping track of progress — <em>“How are we with the go-to-market readiness plans for this major feature? Do we have the support materials in place? Do you need any help there?”</em></li><li>Following up with others who should deliver any dependencies — <em>“Kind reminder that we need that ….”</em></li><li>Changing course when necessary — <em>“Based on product analytics and on what we learned from our customers, it is clear now that this is not gonna fly. We need to sunset this feature and communicate it accordingly to the few customers that use it. ”</em></li><li>Raising flags when they foresee issues — <em>“I did some analysis, and we need to move to the Enterprise package with our … subscription so that we don’t run out of space for the backups. ”</em></li><li>Coming up with ideas to solve blockers and making sure those ideas get implemented — <em>“What if we would try …! I researched a bit, and I think we can do it within a sprint. This way, we will save money later on.”</em></li><li>Measuring success — “<em>I took a look into our analytics, and it was so great to see our lead indicators moving up.</em>”</li><li>Sharing learnings — “<em>Hey guys, let’s have a session about our latest learnings from the user interviews, I think this impacts everyone”.</em></li></ul><p>How can you assess this? One can start the conversation by sending a company-level survey or raise this topic in each team, starting of course, with the Core team (the Leadership team):</p><ul><li>Question 1:<em> “To what extent do I feel a strong sense of ownership over the success of our product? (1 to 10)”</em></li><li>Question 2: <em>“What would I need in order to feel a stronger sense of ownership over the success of our product?”</em> <br>-&gt; for leaders: <em>“What would I need to do so that my team members feel a stronger sense of ownership over the success of our product?”</em></li></ul><h4>2- Give clarity in terms of what you want to achieve and how you envision getting there</h4><p>For us, as human beings, it all starts with the inspiration. Why wake up in the morning and go to work? How will that give me purpose? Does it make sense to me? Is it aligned with my values?</p><p>Clarify your company’s values, mission, vision, and strategic path (big winning moves), and make sure everybody on the team shares this understanding. Do not be afraid to over-communicate it.</p><h4>3- Clarify your roles, expectations, and decision spaces</h4><p>After you have clarified the direction, you need to give your team members a personal mission directly related to the outcome and to make sure they have the skills and tools to run with it. That means clarifying the roles, the expectations, and their decision spaces.</p><p>We all need to openly hear that we are trusted to deliver something that we care about and that we are responsible for it.</p><h4>4- Shut down the impulse to micromanage</h4><p>We simply do not have the time or the skills to do everything ourselves. When we give someone else a problem to solve, they might do it differently than we would approach it. Sometimes we would agree with their approach; other times, we would find ours to be better.</p><p>Trusting others with the outcome of our own company is not something to be taken lightly. Yet, it is probably the only way to achieve outstanding results and create a culture that will be passed on to newcomers.</p><p>That should not mean that leaders will not assess the results of their team members’ work, or that they will not mentor and support their team members in their growth path. It is actually the opposite.</p><p>Leaders need to be able to mentor and coach their teams, support them when needed based on their level of seniority, and only let them ‘fail’ in a controlled environment.</p><h4>5- Give people problems to solve, not solutions to implement</h4><p>Everybody in a startup should feel like an entrepreneur. Because this is what they are. And the best thing entrepreneurs do is to create value and solve important problems.</p><p>There is a world of difference between giving the team an already digested solution, to implement and giving them a problem to solve. The first one is generating an output-driven mindset, losing the connection to the value you hope to generate. The latter enables people to be creative, take a holistic view of things, and find the best path to solve the problem at hand.</p><p>As an example, consider these two approaches:</p><p>“<em>We need to implement a new a 3-step onboarding instead of 5-step</em>” <strong>vs.</strong> “<em>We need to optimize onboarding in order to increase the trial-to-pay conversion by 1% by the end of the quarter</em>.”</p><p>The first way of giving work is limiting, the second way is empowering.</p><h4>6- Promote and value ownership and a bias toward action</h4><p>Create the habit of giving kudos to those who show a high level of ownership and entrepreneurial thinking and the same to those ready to support their colleagues. Reaching hardcore objectives is not a lone-wolf endeavor, it requires the whole tribe to support each other for the greater good.</p><p>Call out the bystander effect if you see it — like, for instance, when you ask, “<em>Who will document in Confluence the decisions we make today?” </em>or <em>“Who will follow up on the action items?</em>” and nobody in the room raises the hand. Use these opportunities to call out the desired behavior you would like to see, which is vital for the success of the company.</p><h4>7- Leadership leads by example</h4><p>There are a few simple things that all leaders in a company can do, to lead by example when it comes to ownership. One of those is “doing what you say you’ll do”. Keeping promises and being consistent with oneself are behaviors that people need to see in their leaders. They will care about the work as much as you do, if you show them how much you care.</p><h4>8- Enable collaboration and open communication</h4><p>People who feel part of the tribe will most likely feel responsible for the tribe’s outcomes. The more team members feel welcomed, valued, and able to contribute — the more they will want this to be successful.</p><p>Open communication, candid feedback, and collaboration based on respect are behaviors you should reinforce, praise and support.</p><h4>9- Make sure your team members grow and develop personally and professionally</h4><p>People who feel they are evolving, learning, and growing personally will more likely have an emotional connection with their workplace. So, allow them the time and resources to develop themselves.</p><h4>10- Keep assessing, re-iterating, re-enforcing</h4><p>Changing mentalities is a process. It is not linear; it has ups and downs, and it requires consistent re-enforcing. Find your multipliers your champions inside each team, and rely on their help to reinforce the desired behaviors.</p><h3>III. Insights</h3><p>Ensure that roles empower but do not limit. Watch out for signs of “that’s not my job ” syndrome. One classic example of that is when a developer says ‘<em>no</em>’ to testing because she/he is not a QA. This is one behavior that needs to be addressed immediately in retros with honesty and respect.</p><p>If you see any signs of already instilled learned helplessness, approach it immediately. Check out the article at the end of this document for more insights.</p><h3>IV. Reflection space</h3><ol><li>Based on what you read so far, what are 2 important things that you take with you?</li></ol><p>……………………………………………….………………………………………………..</p><p>……………………………………………….………………………………………………..</p><p>……………………………………………….………………………………………………..</p><p>2. What are 3 things you can immediately do, already this week, to work on your team’s sense of ownership?</p><p>……………………………………………….………………………………………………..</p><p>……………………………………………….………………………………………………..</p><p>……………………………………………….………………………………………………..</p><h3>V. Further must-reads</h3><ul><li>“No rules rules” — <a href="https://www.amazon.de/-/en/Reed-Hastings/dp/1984877860">https://www.amazon.de/-/en/Reed-Hastings/dp/1984877860</a></li><li>“Radical Candor: How to Get What You Want by Saying What You Mean: How to be a great boss without losing your humanity” -<br> <a href="https://www.amazon.de/-/en/Kim-Scott/dp/1509845356">https://www.amazon.de/-/en/Kim-Scott/dp/1509845356</a></li><li>“The five dysfunctions of a team” <br>- <a href="https://www.amazon.de/-/en/Patrick-M-Lencioni/dp/B09L5M1C21/">https://www.amazon.de/-/en/Patrick-M-Lencioni/dp/B09L5M1C21/</a></li><li>Article on learned helplessness: <br><a href="https://medium.com/@ioanaa.cristinaa/the-path-from-learned-helplessness-to-empowerment-41c50335e016">https://medium.com/@ioanaa.cristinaa/the-path-from-learned-helplessness-to-empowerment-41c50335e016</a></li><li>SCARF model — David Rock<br> <a href="https://www.mindtools.com/akswgc0/david-rocks-scarf-model">https://www.mindtools.com/akswgc0/david-rocks-scarf-model</a></li><li><a href="https://davidrock.net/david-rock-publications/">https://davidrock.net/david-rock-publications/</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=aa0ffd6ab431" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Big product organizations— what to look out for during the PM interview]]></title>
            <link>https://medium.com/@ioanaa.cristinaa/big-product-organizations-what-to-look-for-during-the-interview-1a45d8c48e8?source=rss-6d4cac561a1c------2</link>
            <guid isPermaLink="false">https://medium.com/p/1a45d8c48e8</guid>
            <category><![CDATA[pm-interview]]></category>
            <category><![CDATA[product-organizations]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Ioana Ognibeni (Marinescu)]]></dc:creator>
            <pubDate>Thu, 23 Feb 2023 18:36:49 GMT</pubDate>
            <atom:updated>2023-02-24T15:09:24.795Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*JErVBfLSn84iyOj3" /><figcaption>Photo by <a href="https://unsplash.com/@yogidan2012?utm_source=medium&amp;utm_medium=referral">Daniele Levis Pelusi</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>There is a world of difference between working as a PM in a startup vs. in an established, large product company. While the PM job is, in theory, the same everywhere, the specifics of working in a large company can be unexpected the first time you end up in such a setup.</p><p>There are many reasons why working in a big product corporation adds value to your career:</p><ul><li>you get exposed to scaled-up products and teams,</li><li>can experience the thrill of seeing your product in the hands of millions of users,</li><li>meet other experienced professionals from whom you can learn a great deal.</li></ul><p>Nevertheless, a product organization with &gt;10–15 Product Managers working with their teams on a single product/codebase might face some interesting challenges.</p><p><strong>Here are a few things to watch out for based on my own experience before considering taking on a new role in this setup:</strong></p><h4><strong>#1 The PM team’s cohesion and ability to drive the product toward the product vision</strong></h4><p>A cohesive PM team should translate into the following:</p><ul><li>Fast and uncomplicated decision-making.</li><li>PMs support each other in dealing with cross-team dependencies or team allocations.</li><li>PMs stand united when facing disruptions from top management or organizational changes.</li><li>A shared feeling that individuals trust each other enough to have healthy conflicts, learn together and move the needle in the same direction.</li></ul><p>The pre-requisite is the existence of a product vision and a set of guiding strategic principles. By that, I don’t mean just a lofty phrase but an actionable, applicable system that drives everyday decision-making. All PMs should be on board with the product vision and strategy and share a common understanding.</p><p>Secondly, it implies an (as good as possible) clear separation of ownership inside the product. Of course, stepping on each other’s toes is inevitable, even when that is the case. The question is how well we will deal with that when it happens, and will we be able to put the common good above our egos?</p><p>Thirdly, the PM team should be precisely that: a team, which means there is enough trust to have healthy conflicts, which can lead to learning, commitment, and accountability.</p><p>This aspect might not be easy to figure out during the interviews, but you can glimpse it by asking the right questions and reading the room.</p><h4><strong>#2 Cross-team dependencies</strong></h4><p>I cannot stress enough the need to build teams that have end-to-end responsibility for discovering, delivering, and measuring a feature’s value to the users.</p><p>Sometimes, the split between teams is so bad that everything you try to do gets hit by a wall of dependencies. An example is when teams are split per architectural layers (Front End, Middleware, Back End). Literally, everything you want to deliver to the user has to be touched by several teams.</p><p>In other cases, the intention is to give teams accountability, but the product’s history stands in the way.</p><p>In one of my previous jobs, despite working in a Spotify model and trying our best to separate the areas of responsibility, there were still many cross-team dependencies. For example, in order to deliver a feature that touched 3 endpoints (web, mobile, native), I had to coordinate the work of 5 teams: my team, 2 other feature teams, and 2 platform teams.</p><p>The truth is that you sometimes feel you are doing more project work than product work: making sure the stories required for this feature had priority in the other teams’ backlog, planning what should be done when, by which team etc.</p><p>Make sure you figure out beforehand how the teams are split and what level of dependency exists between them.</p><h4><strong>#3 Product consistency</strong></h4><p>Ensuring a unified experience to the users is also a challenge in a big organization. Product, UX, dev, product marketing — all need to be coherent within their chapters but also cross-chapter.</p><p>Be curious about how the teams manage to keep the product coherent, their struggles, and how they feel about it. Also, try out the product yourself if you can, it is always very revealing.</p><h4><strong>#4 Decision-making authority</strong></h4><p>In large corporations, it is not uncommon to have the decision-making power diluted between many management levels inside the product organization.</p><p>One specifically unfortunate situation is when the Product role is split between a ‘Product Manager’ and a ‘Product Owner’ role. This is one of the biggest fallacies in the product world because it incapacitates both roles. In this case, the development team becomes a bitter feature factory, spending their time in Retros ventilating about how much they would want to make decisions themselves and get to talk to the users directly, while the PM will complain that the features she requested are not delivered fast enough.</p><blockquote>Everyone’s focus moves away from creating value to solving self-made internal frictions.</blockquote><p>Another essential thing to watch out for is the relationship Product-Sales. And that can be very relevant even in a PLG company; how often do features get delivered because “<em>Sales says they are blocked, they cannot reach their target without this feature</em>”? If this is the modus-operandi, it should raise a big flag.</p><p>The extent to which you and your future team will be really driving the product depends very much from company to company, and it is something you may want to figure out from the initial interviews for the role.</p><h4><strong>#5 Speed at which strategy is changing</strong></h4><p>You may want to learn about the past few years and the company’s highlights. What I experienced in larger companies is a certain “instability” of the strategy: products frequently moving between offices/countries, products being shut down unexpectedly, and managers coming and going.</p><p>Do your research about the company, and define for yourself if this is something you can cope with (or even look for).</p><h4><strong>#6 Being in contact with the actual users</strong></h4><p>There is a big trap in spending too much time in internal meetings, syncs, alignments, quarterly plannings, and status reports and not having time for the important things anymore — like talking to your users. I made this mistake, and I regretted it dearly.</p><p>You may want to figure out how often the other PMs and dev teams are in touch with the actual users.</p><h4><strong>#7 Highly specialized aspects of the PM role</strong></h4><p>Large companies tend to have highly specialized departments for various product aspects: customer research team, analytics team, pricing team, several flavors of product marketing etc.</p><p>As a Product Person, you will be less involved in these aspects yourself. Nevertheless, you will have the chance to learn from highly specialized professionals.</p><p>Be curious about the company structure, how various departments cover all these product-related aspects and how they collaborate with each other.</p><h4><strong>#8 Room for trial and error</strong></h4><p>Working on an established product with a lot of visibility in the organization can feel like walking on thin ice.</p><p>If you want an environment where you can fail fast and learn from mistakes, remember to ask for specifics when going for the job interview: <em>how is the fail-fast mentality implemented in the company?</em></p><p>On another note, very bluntly put, it is not unexpected to see the PM structure severely re-organized when things go south with the stock value. If it happened already in the history of the organization, chances are it may happen again.</p><p>Figure out how important this aspect is for you and to what extent your future company can give you what you need.</p><p>As Product Persons, we all want to do something that makes sense to the world and do it right. It is up to us to find a company where we can learn, strive, deliver value, and get energy out of our work. There is no one-size-fits-all. It’s up to us to figure out what environment we need to succeed.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1a45d8c48e8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The path from learned helplessness to empowerment]]></title>
            <link>https://medium.com/@ioanaa.cristinaa/the-path-from-learned-helplessness-to-empowerment-41c50335e016?source=rss-6d4cac561a1c------2</link>
            <guid isPermaLink="false">https://medium.com/p/41c50335e016</guid>
            <category><![CDATA[empowerment]]></category>
            <category><![CDATA[learned-helplessness]]></category>
            <category><![CDATA[david-rock]]></category>
            <category><![CDATA[leadership-coaching]]></category>
            <category><![CDATA[scarf-model]]></category>
            <dc:creator><![CDATA[Ioana Ognibeni (Marinescu)]]></dc:creator>
            <pubDate>Thu, 02 Feb 2023 15:34:53 GMT</pubDate>
            <atom:updated>2023-02-02T15:52:38.315Z</atom:updated>
            <content:encoded><![CDATA[<h4>How leaders influence the relation people have with their own power</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*BvJM78PxDhlD4Naf" /><figcaption>Photo by <a href="https://unsplash.com/@agni11?utm_source=medium&amp;utm_medium=referral">Sivani Bandaru</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Have you ever joined a new company or department full of enthusiasm, only to discover that your new colleagues don’t have any faith in the changes you suggest?</p><p>Some might say that explicitly, while others just shake their heads in disbelief.</p><p>You bring arguments, share your experience, and suggest ways forward, but the only thing you hear back is:</p><ul><li>“<em>We tried that many times before; it will not fly</em>”;</li><li>“<em>The last guy in your role also tried that</em>”;</li><li>“<em>In our company, this is simply impossible.</em>”</li><li><em>“You will also give up, as the rest of us did.”</em></li></ul><blockquote>This phenomenon is called “<strong>learned helplessness</strong>.” It can eat a company’s heart out.</blockquote><p>People learn that they do not control what happens to them and around them and give up trying. They become passive and stop believing in their own competence. Moreover, they will push down any initiative to improve things and demotivate the newcomers.</p><blockquote>How do we end up in this situation?</blockquote><p>Some theories suggest it is related to a certain pessimistic outlook of individuals mixed with the company’s culture.</p><p>It is, in fact, tremendously related to leadership’s actions and inactions.</p><h3><strong>These are six antipatterns I saw time and again leading to this outcome:</strong></h3><h4><strong>#1. Set unclear goals, or change them every day.</strong></h4><p>When leaders cannot offer a clear direction, they set their team members up for failure. People who repeatedly fail to reach their goals end up with low self-esteem and frustration.</p><p>At the same time, moving targets make them feel they cannot reach their goals, no matter what they do. They conclude that goals cannot be achieved, despite all efforts.</p><h4><strong>#2. Ask for people’s opinions, but never consider them in decision-making.</strong></h4><p>Some leaders show interest in the team members’ views and expertise when trying to make a decision. They gather input, facilitate workshops, and do extensive surveys. Yet, when it comes to making the decisions, they don’t consider this input and provide no explanation.</p><p>When this happens repeatedly, people learn that their opinions are not influential and their experience is not important. Therefore, they will eventually stop offering their contribution.</p><h4><strong>#3. Allow or even promote toxic behavior.</strong></h4><p>I’ve seen cases when people with aggressive and bullying behavior are allowed to be in a company only because management perceives them as knowledge holders or indispensable.</p><p>The other individuals put up with that because they see it’s useless to complain about it. Despite their increasing stress level, they accept it is a given thing.</p><p>They conclude this is how things are, and nothing will ever change.</p><h4><strong>#4. Declare something but do precisely the opposite.</strong></h4><p>The first thing that comes to mind here is “agile transformation.” The management claims the company is set to “become agile” and hires new people who should drive this effort.</p><p>At the same time, the management wants to maintain the status quo and not give up on control. So they end up blocking any attempt to move in the new direction.</p><p>The new hires leave after one year, and the remaining team members see that “<em>nothing ever changes around here.</em>”</p><h4><strong>#5. Do not praise or compensate for high performance.</strong></h4><p>When people go the extra mile to contribute to the company’s success, they implicitly expect that leadership will see that and praise them for it.</p><p>When high performers are not receiving recognition, they receive the message that their actions have no value, no matter how successful they are.</p><h4><strong>#6. Make micromanagement the norm.</strong></h4><p>When managers control what their team members think and do to the smallest detail, they give them the message, “you are not able to do it yourself.”</p><p>Those who choose to stay in this abusive scenario will introject this message and believe they do not have the ability or the needed competence.</p><p>They will learn they are not good enough and feel helpless without their manager.</p><h3><strong>What can we do about it?</strong></h3><p>Not falling in these 6 antipatterns is vital in not promoting learned helplessness inside the organization. If any of these is present inside a team, it has to be immediately corrected.</p><p>Additionally, <strong>David Rock’s SCARF model</strong> is a great tool for promoting reward and self-efficacy and reducing stress.</p><p>In a nutshell, it implies that five domains of human social experience are crucial for motivation, efficiency, and empowerment:</p><ul><li><strong>Status</strong> — our position in relation to others,</li><li><strong>Certainty</strong> — our ability to predict the future,</li><li><strong>Autonomy</strong> — our sense of control over events,</li><li><strong>Relatedness</strong> — our emotional safety inside the tribe,</li><li><strong>Fairnes</strong> — our perception of justice regarding the processes and dynamic between individuals.</li></ul><p><em>More details: </em><a href="https://davidrock.net/publications/"><em>https://davidrock.net/publications/</em></a></p><p>In a company, learned helplessness is a killer; its victims are courage, curiosity, ambition, and, eventually, the company’s success.</p><p>Leaders need to be mindful of what message they convey through their behavior, through what they do, and what they don’t do.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=41c50335e016" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to improve your relationship with time in a productivity-obsessed world]]></title>
            <link>https://medium.com/@ioanaa.cristinaa/escaping-the-productivity-obsession-bef7e5a9203a?source=rss-6d4cac561a1c------2</link>
            <guid isPermaLink="false">https://medium.com/p/bef7e5a9203a</guid>
            <category><![CDATA[productivity-hacks]]></category>
            <category><![CDATA[transactional-analysis]]></category>
            <category><![CDATA[efficiency-tips]]></category>
            <category><![CDATA[coaching]]></category>
            <dc:creator><![CDATA[Ioana Ognibeni (Marinescu)]]></dc:creator>
            <pubDate>Thu, 19 Jan 2023 09:25:52 GMT</pubDate>
            <atom:updated>2023-02-23T16:44:40.927Z</atom:updated>
            <content:encoded><![CDATA[<h4>When we need to look beyond all advice and techniques</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*s3r85yG6SgUQeY3x" /><figcaption>Photo by <a href="https://unsplash.com/@timothycdykes?utm_source=medium&amp;utm_medium=referral">Timothy Dykes</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>We live under the Empire of Speed: hyper-growth, velocity, high-speed-everything... It’s easy to feel unproductive and slow when looking around you. At the same time, we have more distractions than ever, and more and more product management brainpower is put into getting users hooked on all sorts of induced behaviors.</p><p>That, of course, opens up a market. We are bombarded with productivity advice and articles on how to:</p><ul><li>Be more like a certain billionaire who works 120 hours per week (sic!).</li><li>Expand your day to last more than 24h.</li><li>Spare time while sleeping less, “optimize” your communication to only 50 essential words, wear the same t-shirt daily (shower less? :P), etc.</li></ul><p>While time management tools are undoubtedly helping optimize your work, many other tips &amp; tricks are either absurd or hilarious.</p><p><strong>Much of this advice is based on a couple of false premises:</strong></p><p>1. <em>That faster equals more value</em>. This is not true. We don’t have to do more in the same amount of time, but do more <strong><em>impact </em></strong>work and/or do it more <strong><em>focused</em></strong>.</p><p>2 . <em>That productivity is the no. 1 value for everyone</em>. Again false. Different people might value other things, despite the massive pressure on all of us to pray to the god of productivity.</p><p>3. <em>That it is enough to </em><strong><em>know</em></strong><em> tools&amp;techniques to actually </em><strong><em>be </em></strong><em>productive.</em> Again, nope, it’s not enough.</p><h3>When even solid techniques fail us</h3><p>As a big fan of time management, I love that it offers a lot of practical techniques we can benefit directly from:</p><ul><li>how to organize your calendar, set up working slots, and book time also for the hidden tasks,</li><li>how to optimize your meeting practice,</li><li>how to make use of the Eisenhower matrix to focus on what matters (my fav),</li><li>how to “eat the frog” and do the most unpleasant tasks first,</li><li>when to use the Pomodoro technique to do focus work, etc.</li></ul><p>Yet, despite the efficacity of these proven tools, many of us still procrastinate or feel inefficient.</p><p>Fundamentally, these tools and techniques make sense when you realize you should organize yourself better or learn new behaviors that help keep you focused.</p><blockquote><strong>But when the problem has to do with <em>unconscious fears or failure</em>, <em>lack of perspectives</em>,<em> lack of meaning, not feeling good enough,</em> <em>not feeling psychologically safe in your workplace, </em>etc. — all these pieces of advice produce only frustration.</strong></blockquote><p><strong>Let me give you an example:</strong></p><p>Y<em>ou have been working on your Ph.D. paper for five years already. You used to love the topic, but now the work is a total pain. You want it done but don’t want to do it anymore. Thinking of it makes you feel sick.</em></p><p><em>Time management techniques may not help in this case. However, suppose you are willing to dig into your thoughts and feelings honestly. In that case, you might discover surprising things like:</em></p><ul><li><em>you never wanted to do a Ph.D. but felt the peer pressure</em></li><li><em>you lost the passion for the topic</em></li><li><em>you are afraid that after it’s done, you will not know what to do next</em></li><li><em>you fear that once you deliver it, it will be less impactful than you hoped, etc.</em></li></ul><p>When we are utterly unsatisfied with our work focus, we need to look 360 degrees at the context in which we are.</p><p>The visible pain could be that we either postpone essential tasks for later, feel burdened with too many things to do simultaneously, or spend too much time scrolling through the news. But this is only the <strong><em>effect</em></strong>.</p><p>Where does the <strong><em>cause </em></strong>lay? Too often, this is <strong><em>not</em></strong> due to our inability to be disciplined, our lack of time management training, or our laziness.</p><p>The reason might lay somewhere else.</p><h3>Several forms of passivity</h3><p>There are several ways in which a lack of productivity manifests itself:</p><ul><li>‘<strong><em>over-adaptation</em></strong>’ — either doing other people’s jobs on top of your own or being too much of a perfectionist</li><li><strong><em>‘agitation</em></strong>’ — doing a lot of unimportant stuff</li><li>‘<strong><em>doing nothing</em></strong>’ — being blocked, confused.</li></ul><p>According to Transactional Analysis, they are all forms of <em>passivity</em>. They are the opposite of actually solving the problem at hand, and to deal with them, we need more than just a couple of productivity techniques.</p><h3>#1 — Over-adaptation</h3><h4><strong>1.1 — Doing tasks that are not your responsibility to do, and losing focus of what you should be doing</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*axVHKGqLFJHO0btk" /><figcaption>Photo by <a href="https://unsplash.com/@kerwinelias?utm_source=medium&amp;utm_medium=referral">Kerwin Elias</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>It’s simple: you are mainly doing other people’s jobs.</p><p>There are many causes for accepting work that should be outside your responsibility: unclear role definitions, fuzzy personal boundaries, times of high uncertainty, and missing agreements.</p><p>However, they all happen with your conscious or unconscious acceptance and have to do with you being in the savior mode.</p><p><strong>If you know you tend to take over more responsibilities than you should, ask yourself:</strong></p><ul><li>“Am I the right person to solve this?”,</li><li>“Do I have all the skills, data, and authority to solve this?”,</li><li>“Knowing this is not my task, do I still want to deliver it myself? Why?”,</li><li>“What do I think will happen if I stop doing things which are actually not my responsibility?”</li></ul><h4><strong>1.2— Over-perfecting something that does not require it</strong></h4><p>Going again and again over something that you should have shipped already. You feel a significant amount of stress thinking it is not yet perfect. And the key word here is <em>perfect</em>.</p><p><strong>When feeling like you’re unable to get done with a task, you could ask yourself:</strong></p><ul><li>“What is realistic/pragmatic for me to do in this situation?”</li><li>“What is <em>expected </em>of me regarding this deliverable/in this situation?”</li><li>“How can I bring the most value through my time?”</li><li>“What do I <em>want</em> to do in this situation?”</li><li><em>“When</em> do I think that I will be satisfied with the result of my work?”</li></ul><h3>#2 — Agitation</h3><h4>Compulsively doing things you know that are neither important nor urgent and leaving aside important ones</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*eqvfTU58p-fg7gc3" /><figcaption>Photo by <a href="https://unsplash.com/@susan_wilkinson?utm_source=medium&amp;utm_medium=referral">Susan Wilkinson</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>The To-Do list is only getting bigger, but you can’t stop doing non-important, non-urgent tasks or scrolling through random things.</p><p>Sometimes, one feels insecure about starting with important tasks or is too afraid of failing. Or we may be physically and mentally tired and have no more energy for anything else. Or we are supposed to do things we do not like, do not approve of, or are not aligned with our values and who we are.</p><p><strong>What to do</strong>:</p><ul><li>Understand <strong><em>your </em></strong>reason behind this behavior; procrastination can have multiple causes, and it is essential to get clarity into why <em>you</em> are procrastinating.</li><li>Are you too tired? Then, first rest. It may be the opposite of what your mind thinks you should do, but it may be what you need.</li><li>Are you supposed to do something against your values or work with people whose behavior is toxic for you? Then reassess your situation and decide if you really want to stay there.</li><li>Are you afraid to start something new? Look into that with self-compassion. What is the worse that can happen if you fail? What is the best that can happen if you succeed?</li><li>Ask yourself: “If I were not doing all this stuff right now, what would I be doing?”</li></ul><blockquote>Note: Working against our core values is damaging and should be avoided.</blockquote><h3>#3 — Doing nothing</h3><h4>Feeling blocked and confused. Spending too much time thinking about how bad you feel not doing anything.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Yc3sGUccQ6HTHkuq" /><figcaption>Photo by <a href="https://unsplash.com/es/@markuswinkler?utm_source=medium&amp;utm_medium=referral">Markus Winkler</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Reading this phrase might sound funny, but it is a very stressful place to be. You feel guilty for not doing enough work, and you spend so much energy and focus on this thought that you have even less time and energy to get work done.</p><p><strong>Ideas on what to do</strong>:</p><ul><li>Be kind to yourself, as simple as it sounds.</li><li>Discover your values and try to do something daily that connects to them. <em>You can take a free values survey here </em><a href="https://www.viacharacter.org/account/register"><em>https://www.viacharacter.org/account/register</em></a><em>. It is a scientifically validated tool that can give many insights.</em></li><li>As a practice, have 5 min time for yourself at the end of the day when you answer these questions:<br>- “What did I learn today?” Scan the day and figure out at least one thing.<br>- “Where did I live my top 3 values?”. Find something that pays towards each of them, even if it is a long shot.</li></ul><p>There is a lot of advice on being more productive or efficient. Some are valid, proper time management techniques, and some are rubbish.</p><blockquote>But when even good advice fails us, it’s time we look deeper. We are real human beings with complex psychology and a universe of beliefs, emotions, desires, and fears that no technique can comprehend.</blockquote><p>This is the time when we need to look in the mirror with courage and compassion and be willing to ask for support if we need a bit of guidance.</p><p><em>As a Coach, I love to accompany my clients through this process. If there is anything I can support you with or if you would like to exchange, feel free to reach out: </em><a href="https://connecting-dots.coach/"><em>https://connecting-dots.coach/</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bef7e5a9203a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[10 learnings on how to run decent interviews]]></title>
            <link>https://medium.com/@ioanaa.cristinaa/10-learnings-on-how-to-run-decent-interviews-770321c530b8?source=rss-6d4cac561a1c------2</link>
            <guid isPermaLink="false">https://medium.com/p/770321c530b8</guid>
            <category><![CDATA[technical-interview]]></category>
            <category><![CDATA[product-manager-interview]]></category>
            <category><![CDATA[interview]]></category>
            <category><![CDATA[interview-tips]]></category>
            <dc:creator><![CDATA[Ioana Ognibeni (Marinescu)]]></dc:creator>
            <pubDate>Sat, 14 Jan 2023 15:49:01 GMT</pubDate>
            <atom:updated>2023-01-16T20:34:05.237Z</atom:updated>
            <content:encoded><![CDATA[<h4>What I’ve learned the hard way while interviewing and being interviewed as a Product Manager</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Jec3MoPeL76XIzGTjKfTWg.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@charlesdeluvio?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">charlesdeluvio</a> on <a href="https://unsplash.com/photos/rRWiVQzLm7k?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>How do you feel about going to an interview? For a long time, I used to feel a knot in my stomach.</p><p>Too many of us are terrified of going through interviews again, although we would like to try out new things/make a career change. And the stress is there for a good reason: many interviews leave you with a sour aftertaste.</p><ul><li>“I had no chance to ask my questions” / “I was given only 10 min at the end for my questions.”</li><li>“I spent 4 hours doing a case study and got no feedback afterward.”</li><li>“The interviewer looked down at me the whole time.”</li></ul><p>An interview is the first opportunity to show your company’s values at work.</p><blockquote>How do you live your core values through the interview experience you offer?</blockquote><p>As an interviewer, I made many mistakes at the beginning of my career. Unfortunately, I was unaware of this at the time. I only realized them when I was again in the candidate position, and the same mistakes were made to me.</p><p>Nobody intentionally creates a bad interview experience, yet this is often the case. The good news is that we can fix it with a drop of good old empathy.</p><blockquote>Interviewing can be a perfect opportunity to exchange and learn from each other, even if we decide we are not a good fit.</blockquote><p>Switching for years between the two sides of the table, I came to these 10 conclusions that I wholeheartedly recommend to interviewers:</p><h3>— before the interview</h3><h4>#1. Make sure the job is really needed/still needed</h4><p>Especially in hyper-grow stages, companies tend to overreact to tiny impulses, while communication breaks easily between departments. The information that a position is no longer needed may not get in time to HR, and they could still be looking for candidates. Or, a super optimistic hiring manager could ask for 5 positions to be filled without validating beforehand that there is a budget only for 2.</p><p>In big corporations, it can be a restructuring or the killing of initiatives that interfere with the open positions. But, unfortunately, the news doesn’t travel fast enough, and departments might still run interviews although those opening are gone.</p><p>Likewise, please ensure you only hire a full-time employee for what is known to be a sure initiative. Someone will leave their current job to come over to you. Let’s not take that lightly.</p><h4>#2. Keep the job description real and to the point</h4><p>Sometimes there needs to be more clarity around roles or what people should do once they come in. For example, each company seems to have its definitions of Product/Project/Scrum master/Business analyst, etc. Clarify what your definition is:</p><ul><li>How does this role pay into your global objectives?</li><li>What is it expected to deliver/drive/achieve?</li><li>What is the decision space? What are the boundaries?</li></ul><p>If you are still a start-up without a clear strategy, and there are many blanks about the role definition, be open and state which points are still to be determined. Candidates will appreciate the chance to collaborate in defining the role.</p><h4>#3. Be open about the salary range</h4><p>Or at least discuss it from the very beginning. I have been through interviews where I stated my expectations from the start. Yet 3–4 interviews later, I’ve learned that the budget was 60–70% of that. I personally do not see any value in this practice, and I doubt it’s driving the expected results.</p><h4>#4. Read the CV beforehand</h4><p>Candidates make time to write an application, and probably spend hours researching your company, your product, your customers, etc. It is a business courtesy to read their CV before getting into the call with them. I know you have many things to do, but it is your job to make time for it, despite jumping between meetings all day long.</p><p>By the way, it is very obvious to an interviewee if you read the CV or not.</p><h3>— during the interview</h3><h4>#5. Build rapport</h4><blockquote>An interview is not about showing rank; it is about building trust. We want to reveal ourselves to each other, not hide or pretend. Only being honest will ensure that both sides can determine whether it is a fit.</blockquote><p>Try starting with a <em>tune-in question</em>: “How do we come into this call today?”. It sets up the tone of the whole conversation. You might learn surprising things about the person in front of you.</p><p>Do <em>active listening</em>. Give your full attention to the candidate, and do not try to multi-task or answer Slack messages during that time. Listen carefully to what they say and to what they don’t say. Reformulate to make sure you understand and make observations.</p><p>Be open and genuine, and above all, be <em>curious</em>. You might end up working daily with this individual — now it’s the time to show up as a real person and see if there is compatibility between you two.</p><h4>#6. Make it a valuable exchange between 2 professionals</h4><p>If there is a single thing I would love you to take from this article, this is it:</p><blockquote>An interview should be a valuable exchange between professionals. It is neither a competition nor a stage for the interviewer to shine.</blockquote><p>No matter the seniority level of the person in front of you, you are talking to another professional. That person might have different experiences than you: not better, nor worse, just different.</p><p>Half of the interview time should be available for the candidates to ask their own questions. I know that you have only limited time together, and for making a decision you want to ask everything at once. But the best way to achieve that is by <em>giving the candidate space to ask questions</em>. This way, you will see their genuine interest and curiosity and witness their thinking process.</p><h4>#7. Come up with interesting questions that lead to a purpose</h4><p>Make sure you have a purpose in mind for what you want to achieve from that interview. Prepare some questions beforehand on various categories e.g., understanding of the role, technical/craft, culture fit, self-awareness, etc.</p><p>Try not to ask the famous “where are you seeing yourself in 5 years”. It is just as relevant as a “5 years product roadmap”. Instead, ask about their ambitions and their drivers. Ask what moves them and what makes them wake up with energy in the morning.</p><p>And please, let’s stop asking about the current salary. I have had enough of that question from all Romanian taxi drivers that take me to the airport in my home town Bucharest. :) You should ask instead how much that person expects as salary and say how much you are ready to offer.</p><h4>#8. The case study</h4><p>I am not a big fan of giving candidates a case study, but I accept that many companies are.</p><p>I believe it is far more interesting to brainstorm on a given topic or find solutions for a given problem — live, during the interview. This is way more revealing to the candidate’s thinking process and approach, at least for Product roles. Note: use this with a grain of salt — introverts will likely prefer more time alone to work out a solution.</p><p>If you plan to ask for a case study/homework, use a <em>hypothetical challenge</em>. That’s also one of the things I learned the hard way.</p><blockquote>Asking the candidates to spend unpaid hours trying to figure out solutions for your current challenges is bad business practice.</blockquote><p>When the candidate presents the case study, you should provide valuable feedback. Ask additional questions, and be curious about what they thought. It is frustrating for candidates to present something they worked on and see little interest from the other side.</p><p>One of the best recruiting experiences I had was one in which I spent a few hours with the actual team, solving a hypothetical challenge. It allowed me to meet my development &amp; UX team, not just the hiring manager. I could see how we interacted with each other, and we had lunch together. I found this extremely useful as a candidate; when I said “yes” to that company, I was already looking forward to working with those from whom I already had such a good vibe.</p><h3>— after the interview</h3><h4>#9. Give and ask for feedback, and do it on time</h4><p>Even if your company does not see the candidate as a good fit at the moment, it is essential to provide feedback. People need to learn from this experience and also to have closure.</p><p>Asking the candidate for feedback and questioning how the recruiting experience was for them can teach you much. Please do not skip this step, you could learn about your blind spots, and it creates the premises for potential collaboration in the future.</p><p>It is a sign of respect to keep your deadlines in providing feedback. Just expecting that candidates will read between the lines if you remain silent is not an OK-OK positioning and might give you a bad reputation.</p><h4>#10. Reflect on the interview — what can you do better next time?</h4><p>Use every interview for a chance to learn and improve. When I write down my notes after the call, I ask myself:</p><ul><li>Where did I do well? Which were the most valuable questions?</li><li>Which part could I have done better? Which questions led the discussion astray? Which formulation was not that inspired?</li><li>What did I learn from this discussion?</li></ul><p>An interview aims to determine the <em>candidate-role fit</em> here and now. To achieve that, I learned the importance of being curious and respectful, being aware of our differences, and showing up authentically in this process.</p><p>We need to create more valuable, helpful, and genuine interview experiences which will ultimately support us in making the right decisions.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=770321c530b8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The deadly ways of ‘risk free’ fixed-price & fixed scope projects]]></title>
            <link>https://medium.com/@ioanaa.cristinaa/the-deadly-ways-of-risk-free-fixed-price-fixed-scope-projects-55710732e2ab?source=rss-6d4cac561a1c------2</link>
            <guid isPermaLink="false">https://medium.com/p/55710732e2ab</guid>
            <category><![CDATA[outcome-over-output]]></category>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[fixed-price]]></category>
            <dc:creator><![CDATA[Ioana Ognibeni (Marinescu)]]></dc:creator>
            <pubDate>Tue, 03 Jan 2023 18:21:02 GMT</pubDate>
            <atom:updated>2023-01-04T14:47:57.273Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*CaA91_alk5OtZdiA" /><figcaption><a href="https://www.pexels.com/@nejc-kosir-108379/">Nejc Košir</a></figcaption></figure><p>Looks like you are responsible for a new initiative in your company<strong> </strong><em>— a new voucher system for your shops, a brand new mobile app, an increment to an existing platform etc.</em>, but your company does not have the required skill set or bandwidth. So you go and engage with a service provider to get that piece of software done.</p><p>You need certainty: the board is only willing to allocate x € into this, and/or the deadline is totally non negotiable. There is pressure and visibility associated with this project. You feel responsible to ensure that your company will not burn money, like so many times before.</p><p>Talking to the service provider, you insist that you want a fixed price-fixed scope project. They may try to talk you into Time &amp; Material, they say something about agile, discovery workshops — too many things that sound too risky or not necessary. You want to know you will get this output within a given budget. The service provider gives up, makes you an offer and you sign it. You think now you can finally relax.</p><p>If this sounds familiar, well — I’ve been there too. Actually on both sides of the deal. What happens next?</p><h3>Case 1. A success story</h3><p>About a decade ago I led a one year e-commerce platform implementation project, with a team of about 20 individuals. We had only a 1 week delay to the planned deadline. We were also pretty much in budget, with only a slight deviation due to change requests. The website looked exactly like in the approved designs (which we had done… one year before that). Great success.</p><p>How did we do it?</p><ul><li>1. We had a trully exceptional team, professionals with experience in this exact <em>mix of industry and technology</em>. They had previously delivered<em> several similar projects</em>.</li><li>2. The <em>complexity </em>of the output was <em>low</em>.</li><li>3. We had state of the art work processes in place, and a <em>strong discipline</em> of project management.</li><li>4. We delivered an intensive<em> 3 months analysis &amp; design phase,</em> before writing the first line of code. We outlined to the smallest detail everything we were about to deliver. Hundreds of acceptance criteria were written and validated with the client. This allowed a quite precise estimation and a good planning of resources. We knew the output in the smallest detail.</li><li>5. We were all young and workaholics.</li></ul><p>The project was successful, but what about the initiative as a whole? I will answer this in a bit.</p><h3>Case 2. A regular story</h3><p>I call the story above an ‘anomaly’. There were too many rare factors involved in the success of that project. The norm is quite different, and looks rather more like this:</p><ul><li>1. The service provider has little to no experience in your industry or technology stack. The estimates will be flaky.</li><li>2. There will be less seniority in the team than you expect.</li><li>3. There will be no analysis phase, as you may not be willing to pay also for one, so the team will make a bunch of assumptions, undocumented, trying to figure out by themselves what you meant by that scope. At this point, the estimates will be rather random.</li><li>4. The team will be put together based on their availability, not necessarily their skillset or specific experience.</li><li>5. The company may not have a strong &amp; clear work process, especially a QA process.</li></ul><p>How does this unfold?</p><p>— Experienced teams will add a lot of buffer into the estimates, so you will end up covering that risk through the project price.</p><p>— Less experienced teams will be optimistic. Happy to get the deal signed, they will agree on a low price and will consume the budget fast. Then they will face the dilemma: pay form their own pocket, or cut something else. As everything is fixed as per the contract, the remaining thing to cut is… <strong>quality</strong>. They might deliver something somewhat working, that carries so much tech debt and poor coding that will eventually be shut down or never used, or rebuilt from scratch.</p><blockquote>Fixed price-fixed scope projects carry more risk than Time&amp;Material, but the risk is hidden. The only certainty in a fixed price-fixed scope project is that when things go south, there will be loss at both ends of the deal.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/587/0*b5fo_2SLu_ERI2B3" /><figcaption><a href="https://www.pexels.com/@jeffrey-czum-254391/">Jeffrey Czum</a></figcaption></figure><h3>Please note that up to this moment I haven’t talked about value and outcome.</h3><p>Was the<strong> Case 1 project</strong> a successful one? Absolutely! But did it deliver a successful <strong>outcome</strong>? I have no clue… we perfectly implemented a 1 year old design and requirements, and hoped for the best. Testing the result, measuring, adapting and improving — everything that would enable thinking about the outcome, was not part of the project scope.</p><p>Fun fact — after the project was delivered, the customer booked an entire team to work agile, and start treating it like a product. Tout est bien qui finit bien… in this case.</p><blockquote>Fundamentally:</blockquote><blockquote>1. Software is simply way too complex to be delivered under the fixed scope scenario.</blockquote><blockquote>2. Even for those rare cases where you <em>can</em> deliver a good output in a fixed price-fixed scope scenario, there will be no focus on ‘outcome’.</blockquote><h3><strong>When to use fixed price-fixed scope</strong></h3><p>— When you are dealing with a complicated environment (e.g. a construction site), not a complex one (e.g. software).</p><p>— When you know exactly what you want to achieve as <em>output</em>, to the smallest detail, and your only interest is the output.</p><p>— When you do not need to continuously inspect and adapt the output, to achieve a better result (outcome) based on learnings.</p><p>— When you do not need to innovate.</p><p>— When it is a <em>small </em>project, preferably<em> very similar</em> to one that the service provider already delivered.</p><h3>What is the healthiest alternative?</h3><h4><strong>1. Be clear what you want to achieve in terms of outcome</strong></h4><p>Start with the “<em>Why</em>”. To which business objective does this initiative relate? In which way?</p><p><strong>Explore the problem space before jumping to the solution space.</strong><em> </em>Do a discovery workshop, look at the opportunities tree — in which other ways could this problem be solved? E.g. Do not ask for help creating an android mobile app with a pink logo, <em>what you need is help creating brand awareness/increasing adoption/decreasing drop-off rate etc.</em></p><p>Share these findings with the service provider, or better — discover them together. Use the collective brain of the team you engage with, to get the most out of it.</p><h4><strong>2. Be willing to accept that there is no such thing as risk-free</strong></h4><p>It is absolutely expected to require a forecast of how much you would need to pay to achieve a certain result. Yet, use it as it is — a <em>forecast</em>. Anybody telling you differently is not telling the whole story.</p><p>Working in small iterations, continousely adapting and using the learnings to improve both the way to work and the way to reach the objective/outcome — this is what can dramatically reduce risk. Working together with users, customers and correctly managing the stakeholders’ expectations — these should also be part of the deal and help mitigate risks.</p><h4>3. Embrace change</h4><p>This is said so often that it ends up sounding like a platitude nowadays, but it is<em> the only way innovation and excellent outcomes come to live.</em></p><p>And by the way, changing minds because of new discoveries and learnings is a sign of doing the right thing in the right way. As hard as it might be to sell this idea to upper management, it will pay off.</p><p>It is absolutely normal to desire safety and certainty when dealing with a service provider, but the environment in which we operate is not one of certainty, but one of complexity.</p><p>So instead of trying to get a deal signed with a company that offers certainty, try to get it signed with a company that offers honesty, proficiency, strong work ethics and a real desire to help you succeed.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=55710732e2ab" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The hard truth about changing jobs, and why I find it healthy]]></title>
            <link>https://medium.com/@ioanaa.cristinaa/the-hard-truth-about-changing-jobs-and-why-i-find-it-healthy-5088c9154aa3?source=rss-6d4cac561a1c------2</link>
            <guid isPermaLink="false">https://medium.com/p/5088c9154aa3</guid>
            <category><![CDATA[new-job]]></category>
            <category><![CDATA[personal-development]]></category>
            <category><![CDATA[job-change]]></category>
            <category><![CDATA[personal-growth]]></category>
            <dc:creator><![CDATA[Ioana Ognibeni (Marinescu)]]></dc:creator>
            <pubDate>Wed, 02 Nov 2022 09:51:33 GMT</pubDate>
            <atom:updated>2022-11-02T21:08:25.419Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JHzTkYweW5RxTLnsQRNT7A.png" /><figcaption>Dall-e generated image - openai.com</figcaption></figure><p>Depending on whom you ask, you will learn that you either changed jobs too often, or not often enough. The answer will be driven by several aspects, like:</p><p>- <em>personal experience </em>— we tend to judge people by the way we deal with these life decisions ourselves<br>- <em>company culture </em>— e.g. is it a start-up or an old family company?<br>- <em>greater cultural space</em> — e.g. is it Europe DACH or North America?</p><blockquote>Whatever you do, according to some opinions you will always have the wrong number of jobs per decade.</blockquote><p>But let’s say you’ve decided to move on and consider another job. How easy is that?</p><p>Job changing is emotionally and mentally expensive. You say goodbye to people you love working with, but also to your product/project you invested so much energy into. At the same time, the thrill of a new adventure can come bundled with stress, and can activate many fears. Impostor syndrome might kick in, doubts could take over your confidence.</p><blockquote><strong>Why even expose yourself to this stress?</strong></blockquote><p>I’ve started my career as a Project Manager, and at that time I was judging my own success only by the difficulty of the project I would bring to life. So I would always be chasing that even harder nut to crack, the next ‘impossible’ project. Later on, as a Product person, I was/am led by curiosity and the need to go where I can bring most value.</p><p><strong>These are 7 hard truths I learned from changing jobs (“too often” by some people’s expectations), and they are the reasons I wouldn’t have done any differently :</strong></p><blockquote><strong>1. Having to prove all over again</strong></blockquote><p><em>The pain:</em></p><ul><li>You are now the newcomer, you need to prove to your team members and leaders that trusting you with the job was a good decision.</li><li>You might no longer be the expert; new systems, new tools, new customers or new ways of doing business that you now have to learn. This might feel uncomfortable, especially since in your old job you used to be the go-to person. Your ego will take a big hit.</li><li>You think you will always get the benefit of the doubt from your new colleagues? Think twice. Not everybody is the same, some people tend to be more strict about who they put their faith in. You will be challenged, and you will have to keep up being calm and assertive, humble yet aware of your self worth.</li></ul><p><em>The gain:</em></p><ul><li><strong>Courage</strong>. You will have to be at your best, walk the talk, connect the dots fast and prove that you live up to your personal values.</li><li><strong>Knowledge</strong>. No matter how similar the new job is to the old one, you will have to learn new things, re-learn topics you once learned theoretically but never applied. The more you will be challenged, the more you will learn.</li></ul><blockquote>2. Building from scratch your network inside the company</blockquote><p><em>The pain:</em></p><ul><li>Here nobody knows you. As I‘ve discovered throughout the years, processes are nice and fun but at the end of the day work gets done because people like to work with each other, not because it is written somewhere that they should do so.</li><li>When a new individual comes into a team, the whole dynamic changes: re-norming, re-storming are in order. These are usually not easy steps, but necessary. You will need to find your place in your new home-team: show your value, set the right boundaries.</li><li>Network is vital, and you need to get out of your shell and show up as a real person. There will be cases when you will have to show weakness to people you barely met, not knowing how they will react or interpret that.</li></ul><p><em>The gain:</em></p><ul><li><strong>New friends.</strong> Nothing ties people together so well, as going through tough times and making it as a team. If you are a multiplier kind of person, a solid team member, a coach or leader that genuinely cares for others’ development — then you will gain so many new and rich connections and collaboration opportunities for the future. And remember the world is a small village.</li><li><strong>Self discovery</strong>. Going through this process is such a necessary journey to make, in order to reveal to your self and others your authentic core. The gain is immense.</li></ul><blockquote>3. Exposure to new situations, patterns and anti-patterns</blockquote><p><em>The pain:</em></p><ul><li>You are out of your well-known territory. Another company culture, another way to deal with situations — or different types of situations altogether, because of the new market, industry, responsibilities etc. So much new stuff, so much to digest and learn. And time is of essence.</li><li>Hitting new highs and lows that you never thought possible before: crazy successes at a totally different scale, blessings in disguise, painful new failures, conflicts and weird situations you didn’t even think of before.</li></ul><p><em>The gain:</em></p><ul><li><strong>Intuition</strong>. The more we experience, the better our ‘guts feeling’ gets. The more you get exposed to new situations, the more you get faster at connecting the dots next time, and have intuitive solutions to problems.</li><li><strong>Expertise</strong>. Now you get to see how other processes look like, other organizational setups, other tech stacks. The more you see different ways to solve for the same problem, the more you know how to help your current company out of anti-patterns and into healthy ways.</li></ul><blockquote>4. Exposure to new leadership styles</blockquote><p><em>The pain:</em></p><ul><li>Maybe you got used to your manager’s style, even if you might not have been totally satisfied with your collaboration. Going somewhere else means having to re-build this very important relationship also from scratch. How will you adjust to the new style? How long will it take to “dance” with each other until you and your new manager will get to a trustful relationship?</li></ul><p><em>The gain:</em></p><ul><li><strong>Becoming a better leader</strong>. The experience you have with your leader(s) will dramatically change the way you yourself will behave as a leader one day. There are a couple of good leadership styles out there, but many bad ones. You do not know what you do not know, until you experience it on your own skin.</li></ul><blockquote>5. Going through interviews (and failing some)</blockquote><p><em>The pain:</em></p><ul><li>Exactly, interviews… That process in which your CV might get judged by people who do not understand what your job is actually all about. Or you will be asked to work for free, several hours of your time, to build a case study for a company that will decline your application without explaining why.</li></ul><p><em>The gain:</em></p><ul><li><strong>Self confidence. </strong>You are forced to get better at presenting your knowledge, skills and past successes, without unnecessary modesty. You will also have to clearly describe what you want to achieve next. Some people may call this “selling yourself”, but I personally prefer to think of it as “letting others know what I can bring to the table”.</li><li><strong>Learning to handle rejection</strong>. This is one of the toughest lessons, especially for all of us perfectionists, or people-pleasers out there.</li></ul><blockquote>Rejection is a great teacher. When we stop taking it personally, we see the value it brings. Most of the times, there is simply not a good match at the moment between your offer and needs, and the company’s offer and needs. Is there something you can learn from this?</blockquote><blockquote>If you get rejected for missing skills, this is a good wake up call. You can decide to fill those gaps.</blockquote><blockquote>Interview rejection for lack of chemistry or values mismatch is really good actually, you wouldn’t want that to become a problem later.</blockquote><blockquote>6. Salary negotiation, position negotiation</blockquote><p><em>The pain:</em></p><ul><li>Here you are again, needing to have a salary conversation. Some see it as an opportunity, some as a hurdle. Nevertheless, it is always part of moving into a new job, and you will need to articulate what you want in return for your services.</li></ul><p><em>The gain:</em></p><ul><li><strong>Better negotiation position</strong>. It is sad to acknowledge this, but I saw it way too often in the IT world to not admit it openly: <em>many companies tend to pay newcomers better than existing employees doing the same job</em>. I do not know when this reality will change in the industry, but it is demotivating and counterproductive. So there you go, you might end up finally getting that salary increase you’ve been asking for years.</li></ul><blockquote>Note: Changing jobs only and only for financial or title reasons is unsustainable and truly damaging in the long run.</blockquote><blockquote>A salary growing too abruptly, too soon, can trap you in a golden cage. Moving too fast on the seniority ladder will brutally expose your blind spots/lack of knowledge or skills. You will be out of your depth and potentially damaging for the teams you could end up leading.</blockquote><blockquote>7. Learning to let go</blockquote><p><em>The pain:</em></p><ul><li>You worked so much and so long to bring this product to life, to scale this team, to increase quality in this code base etc. Thousands of hours of work, nights of staying awake and thinking about it. Well, now you say goodbye, and hope for the best.</li></ul><p><em>The gain:</em></p><ul><li><strong>Detachment.</strong> May sound a bit esoteric, but fundamentally nothing really lasts. A certain detachment from our products/work is necessary for our mental wellbeing. Sometimes letting it go makes space for new, improved work, with new energy and innovative spirit.</li></ul><p>No, I will not pretend I know the truth about how often someone should change jobs. We all know our own life situation, financial stability, and needs of security or adventure. Nobody can or should judge that but ourselves.</p><p>Nevertheless, I strongly believe that</p><blockquote><strong>…growth happens mostly when we are out of our comfort zone</strong>.</blockquote><p>Indeed, a new job brings a huge amount of pains and frictions, but there are even more relevant learnings and growing points it brings along.</p><p>If changing jobs is out of the question, then by all means, change at least the context once in a while:</p><ul><li>ask to work for some time from a another office, in another city</li><li>move to another division/team, experience other leadership styles</li><li>move to another project, experience other team dynamics and/or technologies</li></ul><blockquote><strong>Fundamentally, just look for another context where you are no longer the smartest person in the room.</strong></blockquote><p>The only thing we truly own, in a way nobody can take it away from us, is <em>who we are</em> and <em>what we know.</em></p><p>Our attitude, our experience, our continuously polished and improved self, our way to deal with new situations, connect with people, and co-create value inside a team — these are our real assets in nowadays world, this is what we should treasure and grow.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5088c9154aa3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What is your stress face? — From failure, with love]]></title>
            <link>https://medium.com/@ioanaa.cristinaa/what-is-your-stress-face-from-failure-with-love-ad08d1cf2f64?source=rss-6d4cac561a1c------2</link>
            <guid isPermaLink="false">https://medium.com/p/ad08d1cf2f64</guid>
            <category><![CDATA[life-positions]]></category>
            <category><![CDATA[transactional-analysis]]></category>
            <category><![CDATA[coaching]]></category>
            <category><![CDATA[psychological-safety]]></category>
            <category><![CDATA[failure]]></category>
            <dc:creator><![CDATA[Ioana Ognibeni (Marinescu)]]></dc:creator>
            <pubDate>Sun, 18 Sep 2022 13:45:23 GMT</pubDate>
            <atom:updated>2022-09-18T14:39:27.585Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HG1Rfon-KNT9PCrbAtrPMg.png" /><figcaption>OpenAI-generated image</figcaption></figure><p>When things are going as expected and we are navigating in calm waters, we can more easily be the best versions of ourselves. We are functional adults in our professional role, we can assess and decide, and feel that we are in control of what is happening to us.</p><p>Recent discussions made me think: what about when it really goes south? <strong>Who do we become in failure, and how can we ensure we still like that person?</strong></p><p>Failure can be something big, like when that main strategic project ends up being a disaster, when the team missed a very important launch date — but it doesn’t always have to be that dramatic at all. The definition depends on the emotional threshold of each one of us/the type of situations that ‘press our buttons’, but the common trait is that it’s triggering deep feelings of stress.</p><p>Who are we then? Are we satisfied with whom we become, with how our “stress-face” looks like?</p><p>As work-in-progress-human-beings, we can always do better and be better. <strong>We can always learn how to understand ourselves with more clarity, how to accept our current shortcomings, but change the narrative and create space for our future selves to grow.</strong></p><p><a href="https://en.wikipedia.org/wiki/Transactional_analysis">Transactional analysis</a> offers a beautiful model through which we can gain clarity into our own belief system about ourselves and the others.</p><p>There are 4 possible “<strong>life positions</strong>”, combining the way I feel and think about myself and my self worth, <strong><em>and </em></strong>the way I think and feel about the worth and “OK-ness” of the others:</p><ol><li>I am not OK — You are OK</li><li>I am OK — You are not OK</li><li>I am not OK — You are not OK</li><li>I am OK — You are OK</li></ol><p>Although we tend to have a ‘preferred’ life position, shaped by our early experiences as children in relation to our primary caregivers and our understanding of the world, this life position we adopted is not something cut in stone; we are always able to learn how to switch to the healthiest of them (I am OK — You are OK), even if in deep stress this wouldn’t have been our first choice.</p><p><strong>If you want to reflect on your own stress-face, and gain more insights about how you handle negative situations, I suggest you this exercise:</strong></p><blockquote>Think at <strong>one recent failure at work that you have been part of</strong> and try to get back into that situation mentally. Observe your internal dialog, your first thoughts. What feelings are awakened in you, how does your body react to this (do you feel tension). Stay with that feeling and thoughts, don’t try to escape them — and see which of these 4 positions is closer to your to your inner reality:</blockquote><ol><li>“<strong>It’s all my fault!”</strong></li></ol><p><em>I feel over-responsible for everything that went wrong. I go again and again through all that I could have done differently, what I should have known better. I am in a mental loop with no end. I feel anxiety and maybe even somatize it (have trouble sleeping, cannot concentrate and end up making mistakes because of this). The base feelings I feel are guilt, fear and sadness. If there is anger, it is directed mostly against myself.</em></p><p>This is the “<strong>I am not OK — You are OK</strong>” life position. From my years of work experience but also from my coaching practice, I can definitely say this reaction is not rare between high performing professionals, especially women which might have a higher guilt-proneness than men (<a href="https://www.cambridge.org/core/journals/spanish-journal-of-psychology/article/abs/intensity-of-habitual-guilt-in-men-and-women-differences-in-interpersonal-sensitivity-and-the-tendency-towards-anxiousaggressive-guilt/8646A546F01B6ABF51C9C6F1EF0620A1">see also</a>).</p><p>Although guilt has generally a positive function in promoting prosocial behavior, <strong>unjustified guilt — or when mixed with shame — is simply toxic.</strong></p><p>The key here is to understand what it is that one <strong><em>discounts</em></strong>. By “<strong><em>discounting</em></strong>” Transactional Analysis defines the <strong><em>unaware ignoring of important information, relevant for the problem or for the solution</em></strong>. In this case, one discounts the existence of <em>others</em> in that equation, and their potential contribution to the outcome/their lack of contribution to prevent the outcome, but also everything that one actually did well.</p><p>Ask youself: “<em>What was my actual role? What was I really expected to do, and what did I actually do? Which points did I really fail? What about all the things that I actually did well? Can I also see those?”</em></p><p>The non-controllable events that might have occurred are also discounted, same as the processes which were not in place or the systemic issues that might have led to that problem. Although I feel powerless, the underlying fantasy is that <em>I would have been able to do everything right by myself, and yet I failed.</em></p><p>The good news is that we can free ourselves from the fantasy of control and from that of perfection, by<strong> starting to look objectively what it is that we are discounting. </strong>That way, we can get into a healthy learning mode by seeing this situation as an external observer. Once anxiety is diminished, we can be back into our “thinking self” and start leveraging <em>all available resources</em> in order to improve the situation, but also to learn for the future.</p><p>Fundamentally, <strong>the key is to be able to see our self-worth not as something depending on life events and projects outcomes</strong>, but something that we were simply born with and nobody and nothing can ever diminush.</p><p>2. “<strong>You messed it up!</strong>”</p><p><em>I feel an immediate burst of anger directed against those who I think are to blame. I perfectly see their mistakes and everything they could have done to prevent the disaster from happening. They are guilty!</em></p><p><em>I feel I lost all faith in these people and their ability to perform; I think they are simply incompetent. Could be that I consider jumping in, as only I can save what can be saved, or the opposite, I want to leave them alone to fix this by themselves, as if this is their fault!</em></p><p>These beliefs correspond to a life position “<strong>I am OK — You are not OK</strong>”. I feel superior, more competent than you and I want you to see that.</p><p>In this case, several things are also being discounted:</p><ul><li>the personal contribution to the bad outcome/the lack of personal action to change the outcome,</li><li>the value that the other people actually brought to the initiative despite the bad outcome,</li><li>the fact that <em>everybody</em> is prone to make mistakes.</li></ul><p>From the outside, a person running this blaming process in their mind can look threatening for the others, but in reality, there is a reason why we choose to resolve to this life position, and not to look at our own shortcomings: <strong>it is not acceptable for us to make a mistake, because being less than perfect is ‘deadly’, or at least it is a very shameful thing.</strong></p><p>Nothing happens in a void, of course. Everything has to be considered in a context. In addition to the fact that we all grow up developing our own mental patterns, we work and live in a system which is in itself more or less prone to accept that making mistakes is not only human, but the best teacher for improving. <strong>If the system/the company culture is supporting blame games instead of authentically embracing failure,</strong> <strong>fear might drive some of us to go directly into blaming, and lose the opportunity to grow.</strong></p><p>The key here is to learn accept ourselves unconditionally, so that we can handle our role in the failure without the fear of losing our self-worth, but also to become able to <strong>see the other people intrinsic worth, independently from the outcome of their work</strong>.</p><p>3. “<strong>It is a total disaster, there’s no way out of this/ we are doomed/ nobody can help…</strong>”</p><p><em>I feel powerless and diminished, but I also think the same about others. I see no way out and feel totally drained of any energy. My mind is blocked and I cannot think, can only feel the total helplessness around me.</em></p><p>This corresponds to a “depressive position”, where I am not OK in my own eyes, but neither are the others. All of us lost our worth because of this failure, and there is no way we can get it back.</p><p>When we are in this life position, the “<strong>I am not OK — You are not OK</strong>” position, we lost all hope and are no longer able to solve the problem or even less to learn from it. We are absolutely sure there is no way out, and nobody and nothing can make things better.</p><p>When ending up in this life position, the best thing is <strong>to take distance to see things from a different angle</strong>, and potentially seek professional support to help getting to a healthier perspective.</p><p>4. “<strong>We messed this one up big time, we need now to focus on fixing what we can, and then sit down together and learn from</strong> <strong>it</strong>”</p><p><em>I am sad/disappointed, but also activated to bring my contribution in fixing the situation. I know our priorities and there are 2 questions in my mind:</em></p><ol><li><em>How can we fix this?</em></li><li><em>How can we make sure we do not repeat this again? What are the lessons to learn/what are the measures to implement?</em></li></ol><p>This internal dialog corresponds to an “<strong>I’m OK — You are OK</strong>” positioning. I know that both me and everyone else did the best in our ability to prevent this, and that we need to look honestly and openly at what went wrong, so we can do better next time.</p><p>Nobody is losing their intrinsic worth in my eyes, neither myself nor the others; <strong>nobody becomes “less” just because this failure occurred. It is disappointing, but I feel energized and my energy goes into 3 things:</strong></p><ul><li><strong>understanding</strong></li><li><strong>solving</strong></li><li><strong>learning.</strong></li></ul><p>Holding this position even in the worst of times implies not only a strong sense of self-worth, but also an environment where people have the necessary <strong>psychological safety to fail fearlessly.</strong></p><p>If this is already your life position even in deep stress — congratulations. If you are able to get to this position despite your initial automatic thoughts being rather similar to points 1–3, congratulations again. You are in a healthy place, and have what it takes to continue growing.</p><p>Looking at ourselves while in stress-mode is a great learning point in our personal development, but also<strong> a way to empathize with others —</strong> which potentially will lead to growth and a healthier way to experience failure, personally and as a team.</p><p>As we are the same persons in our job-role and in our private lives, becoming better professionals means ultimately becoming better persons, both in relation to ourselves and to the others around us.</p><p><strong>Failure is not only a part of life, but also the greatest teacher.</strong> If we do not live in a place (internally, in our psychological world, but also externally, in the outside environment) where we can <strong>safely, openly and objectively look at our failure</strong>, we will never improve. But if we manage to find that sweet spot, literally nothing can stop us.</p><p><em>I would love to hear your thoughts about healthy experiencing of failure. If you are interested in discussing more, always feel free to contact me: ioana@connecting-dots.coach or </em><a href="https://linkedin.com/in/ioanamarinescu"><em>linkedin</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ad08d1cf2f64" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>