<?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 Emma Willis on Medium]]></title>
        <description><![CDATA[Stories by Emma Willis on Medium]]></description>
        <link>https://medium.com/@emwil?source=rss-c68a894aa2aa------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*hGpk4PDWx1wgOLkuCHoNbg.jpeg</url>
            <title>Stories by Emma Willis on Medium</title>
            <link>https://medium.com/@emwil?source=rss-c68a894aa2aa------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 15:28:48 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@emwil/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[The best tip I have for production leaders trying to stabilise or scale their team.]]></title>
            <link>https://emwil.medium.com/the-best-tip-i-have-for-production-leaders-trying-to-stabilise-or-scale-their-team-99baa6c819?source=rss-c68a894aa2aa------2</link>
            <guid isPermaLink="false">https://medium.com/p/99baa6c819</guid>
            <dc:creator><![CDATA[Emma Willis]]></dc:creator>
            <pubDate>Fri, 29 Apr 2022 09:23:18 GMT</pubDate>
            <atom:updated>2022-04-29T09:23:18.924Z</atom:updated>
            <content:encoded><![CDATA[<p>Every producer plans and manages projects differently because every producer learns on the job.</p><p>Instead of studying best practices, we pick up our knowledge and tools from the other producers around us. Some of what we learn is great; most of it is good enough. But the inconsistency in our approach is a huge problem for leaders trying to scale and grow production teams.</p><p>How do you plan against, optimise or improve a random process?</p><p>You can’t.</p><p>The winning solution is to standardise how you do things:</p><ol><li>Write down what good looks like for every project event (contracting, kicking off, client reviews… etc and so on), are there principles that always guide your decision-making? Are there things that you always plan for or always catch you out?</li><li>Teach your team those principles, standards and rules, make them the expectation. Set performance targets around them.</li><li>Codify those standards into a playbook to create a learning process instead of just a training event (we used Notion, and published some plays on <a href="https://medium.com/signal-noise-publication">Medium</a>).</li><li>Secure long-term adoption of your production standards by using the playbook to onboard new staff, freelancers and clients into your process.</li></ol><p>If you are an EP, Head of Production/Production Director looking ahead at a rapid period of growth or change and you want to chat about building your playbook, DM me for a chat. Happy to share my experience.</p><p><em>Read this post and more on my </em><a href="https://typeshare.co/artofproduction/posts/the-best-tip-i-have-for-production-leaders-trying-to-stabilise-or-scale-their-team--rhuk"><em>Typeshare Social Blog</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=99baa6c819" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What to do when following the process feels painful.]]></title>
            <link>https://emwil.medium.com/what-to-do-when-following-the-process-feels-painful-eb6e7f2c8f9a?source=rss-c68a894aa2aa------2</link>
            <guid isPermaLink="false">https://medium.com/p/eb6e7f2c8f9a</guid>
            <dc:creator><![CDATA[Emma Willis]]></dc:creator>
            <pubDate>Wed, 27 Apr 2022 15:57:27 GMT</pubDate>
            <atom:updated>2022-04-27T15:57:27.199Z</atom:updated>
            <content:encoded><![CDATA[<p>Sometimes, following processes feels hard (like when leads/execs skip out on meetings).</p><p>Or uncomfortable (like the deafening silence during the daily standup).</p><p>Or awkward (like when painfully shy teammates struggle on calls with clients).</p><p>Some teammates don’t like public speaking. Some teammates don’t appreciate having to announce what they’ve been doing to everyone else. Some teammates talk too much!</p><p>When the process you’re running feels like grafting — like you’re trying to put a square peg in a round hole — it’s a signal to change it up, not keep doing it or double down.</p><p>The purpose of a process (any process) is communication; the most crucial aspect of your work with teammates isn’t running the process right; it’s having the right conversation.</p><p>You’re not going to win when the context and conditions push back. The way to succeed (at anything, not just this) is to seek and find the most comfortable path for the team and yourself. Teammates who feel comfortable, safe and supported will contribute.</p><p>For processes to feel more comfortable and effortless, you need to align your actions with the situation. Focus on the conditions — what do they need to produce? In-depth understanding of a complicated subject? High-level awareness of several different things? The goal is whatever process is going to get you there.</p><p>Bonus tips (not rocket science but worth thinking about):</p><ul><li>Execs like conditions that help them feel heard, present options, and when you’re clear and concise.</li><li>Shy teammates like relaxed, low pressure and low-key conditions.</li><li>Awkward teammates like time to figure it out, practice it or think it over beforehand.</li></ul><p>What kind of conditions help you to thrive?</p><p><em>Read this post and more on my </em><a href="https://typeshare.co/artofproduction/posts/what-to-do-when-following-the-process-feels-painful-"><em>Typeshare Social Blog</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=eb6e7f2c8f9a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[It took me ten years to figure out the difference between a producer and a project manager.]]></title>
            <link>https://emwil.medium.com/it-took-me-ten-years-to-figure-out-the-difference-between-a-producer-and-a-project-manager-245090ea7585?source=rss-c68a894aa2aa------2</link>
            <guid isPermaLink="false">https://medium.com/p/245090ea7585</guid>
            <dc:creator><![CDATA[Emma Willis]]></dc:creator>
            <pubDate>Tue, 26 Apr 2022 15:09:57 GMT</pubDate>
            <atom:updated>2022-04-26T15:09:57.857Z</atom:updated>
            <content:encoded><![CDATA[<h3>It took me ten years to figure out the difference between a producer and a project manager. Let me save you the time..</h3><p>Producers do two things:</p><ol><li>Project development — taking the germ of an idea and facilitating its evolution into something feasible.</li><li>Project delivery — planning and execution of the idea.</li></ol><p>We leverage three core skills when we do it:</p><ul><li>Strategic ability</li><li>Entrepreneurial ability</li><li>Project management</li></ul><p>Project development is complex. There isn’t a specific process or series of steps you can follow to create something from nothing. Strategy is a tool for dealing with uncertainty. We use it to help clients achieve results, and producers use it on projects when facing uncertain problems. Producers with strong strategic abilities thrive in chaotic and ambiguous situations.</p><p>The act of creation is so chaotic because it’s an unfolding and emergent process driven by the relationships between people, technology and context. Those relationships give rise to surprising, unexpected and risky opportunities. Producers with entrepreneurial skills are more likely to spot the potential upside. Instead of trying to control the process, they “shepherd the unfolding” of ideas into the most vibrant version of what they could be.</p><p>Project delivery is complicated. There are lots of moving parts. But the production process is like anything else complicated (a car engine, software, flying a plane); once we know what it is and how it works, we can master it. Producers with excellent project management skills can keep even the gnarliest of projects on track.</p><p>After 13+ years of trying to codify a producer’s core skill set, I think this is it. What do you think?</p><p><em>Read this post and more on my </em><a href="https://typeshare.co/artofproduction/posts/it-took-me-ten-years-to-figure-out-the-difference-between-a-producer-and-a-project-manager-let-me-save-you-the-time-"><em>Typeshare Social Blog</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=245090ea7585" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[2 tips to prepare for and manage change on your project.]]></title>
            <link>https://emwil.medium.com/2-tips-to-prepare-for-and-manage-change-on-your-project-24e8aa5640cd?source=rss-c68a894aa2aa------2</link>
            <guid isPermaLink="false">https://medium.com/p/24e8aa5640cd</guid>
            <dc:creator><![CDATA[Emma Willis]]></dc:creator>
            <pubDate>Mon, 25 Apr 2022 08:50:59 GMT</pubDate>
            <atom:updated>2022-04-25T08:50:59.500Z</atom:updated>
            <content:encoded><![CDATA[<p>When it comes to controlling scope creep, your biggest concern should be the people furthest away from the project: dept heads and directors, company leaders. Even consultants and board members. These behind-the-scenes stakeholders have more power and influence to derail your project than the team and even your client POC. They also like to do it at the absolute worst moment 🤣</p><p>It’s incredibly difficult to see the change these stakeholders cause coming down the pike, but if you prepare for it you can lessen the impact it has on production.</p><p>First off is mental preparation. You must always be ready and willing to free yourself from execution. To go off-plan and find a different path. When change happens, take off your project manager hat and put your strategy hat on instead. Start by reconfirming your goals and painting a fresh picture of the end-game to refocus everybody, then switch to asking questions instead of striving to answer them:</p><ul><li>What about this is good for us?</li><li>What about it is bad?</li><li>Could we accommodate the good? How?</li><li>How might we shut the bad stuff down?</li></ul><p>The second type of prep is logistical. Chances are the silent stakeholders know nothing about your project or what you are trying to do, which is what makes it so easy to demand things that are really disruptive — there are no apparent consequences. By onboarding them into the project, you can make consequences explicit and make it harder for them to derail your work.</p><p>One simple method is to produce a project onboarding document that you and your client can share with the senior ranks containing the project details and — this is the important bit — how you both agreed up-front to manage project change.</p><p><em>Read this post and more on my </em><a href="https://typeshare.co/artofproduction/posts/2-tips-to-prepare-for-and-manage-change-on-your-project-"><em>Typeshare Social Blog</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=24e8aa5640cd" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[9 out of 10 producers make this mistake. Are you one of them?]]></title>
            <link>https://emwil.medium.com/9-out-of-10-producers-make-this-mistake-are-you-one-of-them-ed36b07eae7b?source=rss-c68a894aa2aa------2</link>
            <guid isPermaLink="false">https://medium.com/p/ed36b07eae7b</guid>
            <dc:creator><![CDATA[Emma Willis]]></dc:creator>
            <pubDate>Sun, 24 Apr 2022 13:07:39 GMT</pubDate>
            <atom:updated>2022-04-24T13:07:39.224Z</atom:updated>
            <content:encoded><![CDATA[<p>When you’re talking about scope, there’s a massive difference between goals (the outcomes we want), capabilities (how we arrive at the outcomes) and features (what we build to implement the capabilities).</p><p>One of the biggest drivers of scope creep I have seen happens when teams frame discussions about scope with clients through the lens of features instead of capabilities.</p><p>Say your client’s vision is to create a marketplace that matches craftspeople with charities to raise money for good causes. One goal might be to onboard one new charity per week, which means providing the capability for charities to submit their information and join the platform.</p><p>Sign up is the capability.</p><p>Sign up is the scope.</p><p>Now think of all the features you could design and build to enable that capability. There are <em>so many</em> options. Maybe you allow charities to join using a Google account (or not); perhaps you make a custom form to capture campaign information or integrate Typeform. Maybe there’s just one page with a telephone number on it. The list goes on…</p><p>Now here’s the science bit.</p><p>When you talk to clients about capabilities, you avoid locking yourself into specific solutions. If, down the line, you discover the features you were planning are too big for the timeline or the budget, the option is always there to implement alternatives.</p><p>The capability is the scope, not the feature.</p><p>Talk about features with teams and capabilities with clients.</p><p><em>Read this post and more on my </em><a href="https://typeshare.co/artofproduction/posts/9-out-of-10-producers-make-this-mistake-are-you-one-of-them-"><em>Typeshare Social Blog</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ed36b07eae7b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The advice I would give to my 5-years-ago self.]]></title>
            <link>https://medium.com/the-art-of-production/the-advice-i-would-give-to-my-5-years-ago-self-2430ca183fbd?source=rss-c68a894aa2aa------2</link>
            <guid isPermaLink="false">https://medium.com/p/2430ca183fbd</guid>
            <category><![CDATA[creative-production]]></category>
            <category><![CDATA[creative]]></category>
            <category><![CDATA[producer]]></category>
            <category><![CDATA[digital-production]]></category>
            <category><![CDATA[project-management]]></category>
            <dc:creator><![CDATA[Emma Willis]]></dc:creator>
            <pubDate>Sat, 23 Apr 2022 09:16:29 GMT</pubDate>
            <atom:updated>2022-04-23T09:16:29.677Z</atom:updated>
            <content:encoded><![CDATA[<p>Is to start writing.</p><p>It was only through writing that I realised how much more there is to this role than project management; that there are, in fact, three distinct aspects to the work of a producer:</p><ul><li>Entrepreneurship (taking on risks in the hope of profit)</li><li>Project management (planning and execution)</li><li>Creative strategy (finding the right approach to do the above)</li></ul><p>And it was only through discovering those three distinct aspects that I was able to understand my purpose in any project team:</p><p>To balance cost with quality.</p><p>And it was only through understanding that purpose that I could finally, confidently, step into it fully.</p><p>Knowing this stuff brought clarity to every conversation. I grew more confident in the outcome I was striving for with each realisation, able to walk into a room knowing exactly why I was there and what I had to do. It’s a hugely empowering and exhilarating feeling.</p><p>It also opened up a clear pathway for personal growth — with three concrete avenues to dive into, I focused on the area I was weakest (business development) and didn’t look back.</p><p>Now writing has become my business. It has enabled me to abstract all this knowledge into a training programme. It allows me to clarify all the ideas in that training every time I reflect on them to create these posts.</p><p>Writing is what I would encourage for my 5-years ago self as the means to problems, develop ideas and organise how I communicate more quickly and more effectively. If you don’t do it, why not try it?</p><p><em>Read this post and more on my </em><a href="https://typeshare.co/artofproduction/posts/the-advice-i-would-give-to-my-5-years-ago-self"><em>Typeshare Social Blog</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2430ca183fbd" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-art-of-production/the-advice-i-would-give-to-my-5-years-ago-self-2430ca183fbd">The advice I would give to my 5-years-ago self.</a> was originally published in <a href="https://medium.com/the-art-of-production">Art of Production</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The thing I lean on most to get shit done in less time and with less stress.]]></title>
            <link>https://medium.com/the-art-of-production/the-thing-i-lean-on-most-to-get-shit-done-in-less-time-and-with-less-stress-5562c461f611?source=rss-c68a894aa2aa------2</link>
            <guid isPermaLink="false">https://medium.com/p/5562c461f611</guid>
            <category><![CDATA[digital]]></category>
            <category><![CDATA[digital-production]]></category>
            <category><![CDATA[producer]]></category>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[creative]]></category>
            <dc:creator><![CDATA[Emma Willis]]></dc:creator>
            <pubDate>Thu, 21 Apr 2022 07:00:35 GMT</pubDate>
            <atom:updated>2022-04-21T07:00:35.168Z</atom:updated>
            <content:encoded><![CDATA[<p>The skill I draw on most in my day-to-day work as a producer is framework thinking.</p><p>Creative production is messy.</p><p>Ideas thrive on disorder.</p><p>The nature of our work means we don’t often see or feel discernible next steps, and we certainly don’t have all the answers.</p><p>Frameworks provide processes to help us arrive at answers — quickly and consistently with lots of room for creativity. They act as a scaffold, helping to order my thoughts so I can cut through the noise and hone in on the problems behind the problems.</p><p>Using frameworks means I can keep the team focused on the task at hand, so they can focus on how to boss it. Frameworks also provide the team with security and confidence — there’s always a way to do a given thing because there’s pretty much a framework for every problem.</p><p>They are (literally) everywhere. I pin my favourites to a collection on Pinterest, and I go to that board almost every day. After years of capturing my favourites, I have a little library of problem-solving tools right at my fingertips, and each one offers a different perspective on a problem.</p><p>The more lenses you have, the more you can see.</p><p>The more you can see, the more you know.</p><p>The more you know, the quicker you can act.</p><p>Posting some of my favourite frameworks in the comments.</p><p>Would love to see some of the ones you use…</p><p>#framework #creativeproduction #digitalproduction #producerlife #digitalproducer #projectmanager #digitalprojectmanager #tech #creativetech #digital #agencylife #adagency</p><p><em>Read this post and more on my </em><a href="https://typeshare.co/artofproduction/posts/the-thing-i-lean-on-most-to-get-shit-done-in-less-time-and-with-less-stress"><em>Typeshare Social Blog</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5562c461f611" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-art-of-production/the-thing-i-lean-on-most-to-get-shit-done-in-less-time-and-with-less-stress-5562c461f611">The thing I lean on most to get shit done in less time and with less stress.</a> was originally published in <a href="https://medium.com/the-art-of-production">Art of Production</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[One trend I’ve noticed talking to production leaders lately, and what I think it means.]]></title>
            <link>https://medium.com/the-art-of-production/one-trend-ive-noticed-talking-to-production-leaders-lately-and-what-i-think-it-means-9d68e8c6e75c?source=rss-c68a894aa2aa------2</link>
            <guid isPermaLink="false">https://medium.com/p/9d68e8c6e75c</guid>
            <category><![CDATA[digital-production]]></category>
            <category><![CDATA[production]]></category>
            <category><![CDATA[strategy]]></category>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Emma Willis]]></dc:creator>
            <pubDate>Tue, 19 Apr 2022 09:16:18 GMT</pubDate>
            <atom:updated>2022-04-19T09:16:18.413Z</atom:updated>
            <content:encoded><![CDATA[<p>I’ve noticed a trend in recent conversations with production company leaders.</p><p>Teams are getting caught out when the “project” becomes a <em>product</em>, and unscoped, long-term requirements emerge late in delivery.</p><p>Peers have asked, how would I prevent this? Would I implement a hybrid production approach to manage it better?</p><p>The answer is: I would train producers to talk “scope of value” before “scope of work”.</p><p>Prod cos. don’t often engage in long-term agreements with clients. We have spent a lifetime working project-to-project; this is our business as usual. We are so used to it that a) we are not familiar with taking up strategic space, so b) we don’t know how to.</p><p>It means we struggle to ask the qualifying questions that will help us determine what is meaningful about our work.</p><p>The solution to the problem of uncaptured, long-term requirements is for leaders to help teams break free of the short-termism endemic in our business and occupy the mindset of a strategic partner. And that all starts with developing a set of simple, conversational tools to drive those types of conversations.</p><p>Questions like:</p><p>Tell us, will the project create long term (strategic) value or short term (tactical) advantage? Why?</p><p>What will change for you (POC + client) if we succeed?</p><p>What is to you (POC + client) if we don’t?</p><p>We are well-versed in capturing the project and user requirements at the start of the project:</p><p>Deliverables include X</p><p>Users must be able to do Y</p><p>But we neglect to capture:</p><p>The client business must be able to do Z [on delivery]</p><p>If we can teach our teams to surface whether the project is business as usual for the client, the potential to pivot from a short-term to a long-term revenue outlook that product work provides is vast.</p><p><em>Read this post and more on my </em><a href="https://typeshare.co/artofproduction/posts/one-trend-ive-noticed-talking-to-production-leaders-lately-and-what-i-think-it-means--4ga5"><em>Typeshare Social Blog</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9d68e8c6e75c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-art-of-production/one-trend-ive-noticed-talking-to-production-leaders-lately-and-what-i-think-it-means-9d68e8c6e75c">One trend I’ve noticed talking to production leaders lately, and what I think it means.</a> was originally published in <a href="https://medium.com/the-art-of-production">Art of Production</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How I defined success as a producer when I first started vs how I define success as a producer…]]></title>
            <link>https://medium.com/the-art-of-production/how-i-defined-success-as-a-producer-when-i-first-started-vs-how-i-define-success-as-a-producer-7c5c02c0eeb5?source=rss-c68a894aa2aa------2</link>
            <guid isPermaLink="false">https://medium.com/p/7c5c02c0eeb5</guid>
            <category><![CDATA[digital-production]]></category>
            <category><![CDATA[creativity]]></category>
            <category><![CDATA[production]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[project-management]]></category>
            <dc:creator><![CDATA[Emma Willis]]></dc:creator>
            <pubDate>Wed, 06 Apr 2022 08:50:08 GMT</pubDate>
            <atom:updated>2022-04-23T16:33:44.425Z</atom:updated>
            <content:encoded><![CDATA[<h3>How I defined success as a producer when I first started vs how I define success as a producer today.</h3><p>Delivering on time and budget &lt;&gt; Producing work that works</p><p>Sticking to the plan &lt;&gt; Finding the right plan</p><p>Being able to lead a team &lt;&gt; Creating conditions for talent to thrive</p><p>Never getting it wrong &lt;&gt; Not letting my fear of doing it wrong get in the way of trying and doing</p><p>Following the process correctly &lt;&gt; Dismantling process that doesn’t work</p><p>Producing cool projects &lt;&gt; Producing results for clients, colleagues, users and studio</p><p>Controlling client involvement &lt;&gt; Involving the client whenever possible and beneficial</p><p>Communicating confidently with clients &lt;&gt; Helping clients feel heard</p><p>I hadn’t even realised the journey I had been on until we wrote the training for AoP, and I had to put down in words what I did and how I did it. I love this job so much; it pushes me to improve every day.</p><p>Where are you on your journey?</p><p><em>This post was created with </em><a href="https://typeshare.co/?ref="><em>Typeshare</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7c5c02c0eeb5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-art-of-production/how-i-defined-success-as-a-producer-when-i-first-started-vs-how-i-define-success-as-a-producer-7c5c02c0eeb5">How I defined success as a producer when I first started vs how I define success as a producer…</a> was originally published in <a href="https://medium.com/the-art-of-production">Art of Production</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[One question every producer should ask before they reject project change (and potentially miss out…]]></title>
            <link>https://medium.com/the-art-of-production/one-question-every-producer-should-ask-before-they-reject-project-change-and-potentially-miss-out-e64b4c77762c?source=rss-c68a894aa2aa------2</link>
            <guid isPermaLink="false">https://medium.com/p/e64b4c77762c</guid>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[digital-production]]></category>
            <category><![CDATA[production]]></category>
            <category><![CDATA[creativity]]></category>
            <category><![CDATA[tech]]></category>
            <dc:creator><![CDATA[Emma Willis]]></dc:creator>
            <pubDate>Tue, 05 Apr 2022 08:21:36 GMT</pubDate>
            <atom:updated>2022-04-05T08:21:36.424Z</atom:updated>
            <content:encoded><![CDATA[<h3>One question every producer should ask before they reject project change (and potentially miss out on the opportunity it brings)</h3><p>It’s easy to think of all project change as bad, but doing the same old thing is how you end up with the same old thing. It’s why one of a producers’ core skills is knowing when to take risks — because innovation requires a departure from the status quo. Creativity thrives on randomness and disorder, and we need to lean into it if we’re going to capitalise on the opportunity there.</p><p>It starts with being able and confident to go off plan — to make constant course adjustments based on the changing shape and needs of the project context. And the only way to get good at that is (ironically?) changing how you feel about change.</p><p>We fear change, but I think it’s because we haven’t consciously processed that there are different types of change. There’s change we want and change we don’t. Then there’s change we see coming and change we don’t, and you want to be careful not to conflate one type for the other: just because we didn’t expect something doesn’t mean it isn’t desirable. A producer needs to know and spot the difference so the team can act in a way that’ll benefit the project the most.</p><p>All change is disruptive, so judging whether it might be valuable based on convenience will always result in a “no”.</p><p>A better qualifying question is, “How might the disruption be worthwhile?”</p><p>Get the right mix of people around the problem and explore the possible upsides before rejecting it.</p><p><em>This post was created with </em><a href="https://typeshare.co/?ref="><em>Typeshare</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e64b4c77762c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-art-of-production/one-question-every-producer-should-ask-before-they-reject-project-change-and-potentially-miss-out-e64b4c77762c">One question every producer should ask before they reject project change (and potentially miss out…</a> was originally published in <a href="https://medium.com/the-art-of-production">Art of Production</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>