<?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 Malinda Lloyd on Medium]]></title>
        <description><![CDATA[Stories by Malinda Lloyd on Medium]]></description>
        <link>https://medium.com/@malindalloyd?source=rss-329b663b4a1e------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*0RUJKqJxDyf3I6M9.jpg</url>
            <title>Stories by Malinda Lloyd on Medium</title>
            <link>https://medium.com/@malindalloyd?source=rss-329b663b4a1e------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 07:18:27 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@malindalloyd/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[Space — The Final Frontier]]></title>
            <link>https://medium.com/@malindalloyd/space-the-final-frontier-6671596f0cf2?source=rss-329b663b4a1e------2</link>
            <guid isPermaLink="false">https://medium.com/p/6671596f0cf2</guid>
            <category><![CDATA[social-media]]></category>
            <category><![CDATA[marketing]]></category>
            <category><![CDATA[space]]></category>
            <category><![CDATA[twitter]]></category>
            <category><![CDATA[content]]></category>
            <dc:creator><![CDATA[Malinda Lloyd]]></dc:creator>
            <pubDate>Sun, 16 Jul 2017 21:06:01 GMT</pubDate>
            <atom:updated>2017-07-16T21:06:01.429Z</atom:updated>
            <content:encoded><![CDATA[<p>With the recent passing of everybody’s favorite <a href="http://www.nytimes.com/2015/02/27/arts/television/leonard-nimoy-spock-of-star-trek-dies-at-83.html?_r=0">Vulcan</a>, humans <a href="http://www.esa.int/Our_Activities/Space_Science/Rosetta/Touchdown!_Rosetta_s_Philae_probe_lands_on_comet">landing a vehicle on a comet</a>, and more launches from a <a href="http://www.spacex.com/">private enterprise space craft company</a>, it’s hard to ignore the huge leap forward science and technology have taken in gathering interest from the public.</p><p>I first noticed <a href="https://www.nasa.gov/connect/social/index.html">NASA </a>on social media about 5 years ago while attending <a href="http://sxsw.com/">SXSW</a>. They presented an awesome panel on how they engaged with fans of the space program. By inviting their influencers to <a href="https://www.nasa.gov/connect/social/index.html">exclusive events</a> and treating them like honored guests, NASA was able to grow its audience beyond the hardcore science fans.</p><p>These same influencers also brought the Curiosity Rover’s slightly tongue-in-cheek <a href="https://twitter.com/MarsCuriosity">twitter feed</a> to the attention of the mainstream media. Everyone remembers the Curiosity Rover launch, when the world fell in love with one <a href="http://www.slate.com/blogs/future_tense/2012/08/06/bobak_ferdowsi_adam_steltzner_nasa_s_mars_rover_curiosity_team_includes_a_mohawk_guy_.html">adorably punk astronomer</a> and science was cool again, right? <a href="http://memegenerator.net/instance/57034130">Bobak Ferdowsi </a>was suddenly famous.</p><p>What a delight to follow:</p><blockquote><em>No foolin’! These mineral veins are more clues to ancient wet environment at Gale crater. </em><a href="https://twitter.com/MarsCuriosity/status/583402358324858881/photo/1"><em>http://t.co/NCxzyq42nY pic.twitter.com/jbEm29Su89</em></a></blockquote><blockquote><em>— Curiosity Rover (@MarsCuriosity) </em><a href="https://twitter.com/MarsCuriosity/status/583402358324858881"><em>April 1, 2015</em></a></blockquote><p>I credit their attention to content to the increase in coverage of science in the mainstream media. And their follower counts speak for themselves:</p><ul><li>Twitter — <a href="https://twitter.com/intent/follow?source=followbutton&amp;variant=1.0&amp;screen_name=nasa">https://twitter.com/NASA </a>(NINE MILLION + FOLLOWERS!)</li><li>Google + — <a href="https://plus.google.com/+NASA">https://plus.google.com/u/1/+NASA/posts </a>(2.2 millions followers)</li><li>Instagram —<a href="https://www.instagram.com/nasa/"> https://instagram.com/nasa/</a> (2.7 million followers)</li><li>Facebook — <a href="http://www.facebook.com/nasa">https://www.facebook.com/NASA</a> (10 MILLION + LIKES)</li></ul><p>In fact, the explosion in science media led to the <a href="http://www.cnn.com/2012/08/29/us/mars-single/">premiere of a pop song</a> from Mars. Who would have thought that would be possible in our lifetime? Thanks, <a href="http://will.i.am/">Will.i.am</a>, thanks, NASA!</p><p><em>This article originally appeared on MindaOverMedia.net on April 15, 2015 — The site is now retired.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6671596f0cf2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Brand Study — Surly Bicycles]]></title>
            <link>https://medium.com/@malindalloyd/brand-study-surly-bicycles-899746c2a232?source=rss-329b663b4a1e------2</link>
            <guid isPermaLink="false">https://medium.com/p/899746c2a232</guid>
            <category><![CDATA[strategy]]></category>
            <category><![CDATA[marketing]]></category>
            <category><![CDATA[brand-strategy]]></category>
            <category><![CDATA[cycling]]></category>
            <category><![CDATA[brands]]></category>
            <dc:creator><![CDATA[Malinda Lloyd]]></dc:creator>
            <pubDate>Sat, 15 Jul 2017 20:11:00 GMT</pubDate>
            <atom:updated>2018-05-22T16:41:43.446Z</atom:updated>
            <content:encoded><![CDATA[<p>My husband and I are cycling enthusiasts but not spandex-wearing racers; we’re commuters and cargo folks. Starting off 2014 on a hunt for bicycle upgrades, we were looking through the <a href="http://surlybikes.com/">Surly Bikes</a> website and I was struck by how consistent in message, voice and aesthetic the people at Surly Bikes are with their materials.</p><p>The Surly team has chosen a voice and aesthetic that fits itself and its customers — one that is reminiscent of the punk-rock Xerox ‘zines of the 80s and early 90s (think black and white with scratchy text and images). Anyone looking through the myriad of products and content can see this team lives for its tough bikes, and the Surly content even leans toward the inappropriate at times.</p><p>Looking even further into their blog, you can see these guys and gals tell it like it is without compromise and add in a sprinkling of hardcore nerd references. They titled a blog post “<a href="http://surlybikes.com/blog/post/fk_it_lets_go_ride_bikes">F%*l it, Let’s go ride bikes!</a>” There is a treasure trove of fun posts in which all of the Surly staffers share their nicknames — my particular favorite is “Greggity Greg Greg Greggers.”</p><p>Take a look at their names for bike colors–they are playful and sometimes downright gross. Names like “<a href="http://surlybikes.com/bikes/krampus">Moonlit Swamp</a>,” “<a href="http://surlybikes.com/bikes/karate_monkey">Safety Scissors Blue,</a>” “<a href="http://surlybikes.com/bikes/karate_monkey">Stretchpants Black,</a>” “<a href="http://surlybikes.com/bikes/ecr">MRE Green</a>” and “<a href="http://surlybikes.com/bikes/ogre">Blacktacular</a>” are attention-grabbing (and I’ll spare you the gross and suggest if you are that curious, take a look for yourself!).</p><p>The names of their frame models also incorporate the nerd-punk aesthetic; names like “Ogre,” “Troll” and “Krampus” conjure up images of Dungeons &amp; Dragons or J.R.R. Tolkien. My personal favorite product names are applied to their trailers; one is called<a href="http://surlybikes.com/bikes/bill_trailer"> Bill </a>and the other <a href="http://surlybikes.com/bikes/ted_trailer">Ted</a>, bringing back memories of <a href="http://www.imdb.com/title/tt0096928/">the hottest time travel movies</a> from my teenage years.</p><p>As for their manuals, the voice does go all the way through to the documentation. I bought a part for my bicycle and the instructions include the phrases <a href="http://surlybikes.com/uploads/downloads/NewSingleatorInfo.pdf">“Quit whining” and “Go Ride.”</a></p><p>Their <a href="http://web.archive.org/web/20150203224706/http://surlybikes.com//bios/">bios</a> are hilarious and genuine, with personal stories and goofy pictures; try to not read every single o<em>ne!</em></p><p><em>This article originally appeared at MindOverMedia.net on January 29, 2014 — the site is now retired</em></p><p><strong>Edited to add:</strong></p><p><strong>Surly Bikes has named the color of one of their Ogre frames “</strong><a href="https://www.facebook.com/SurlyBikes/posts/1702797876469885"><strong>Rover Brown</strong></a><strong>” after my favorite shop dog at Topanga Creek Outpost!</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=899746c2a232" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Interactive Producing 101: The Lingo]]></title>
            <link>https://medium.com/@malindalloyd/interactive-producing-101-the-lingo-da96ae1a5116?source=rss-329b663b4a1e------2</link>
            <guid isPermaLink="false">https://medium.com/p/da96ae1a5116</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[scrum]]></category>
            <dc:creator><![CDATA[Malinda Lloyd]]></dc:creator>
            <pubDate>Fri, 28 Apr 2017 17:30:26 GMT</pubDate>
            <atom:updated>2017-07-15T17:42:21.823Z</atom:updated>
            <content:encoded><![CDATA[<p>Watch this video before reading any further:</p><p>https://youtu.be/GyV_UG60dD4</p><p>Funny, right? It’s a jumble of jargon but, I’ve attended that meeting and so will you. It is kind of horrifying to sit there and realize that nothing has been said because the sentences were full of made up buzz words. Believe it or not, some of that jargon does have purpose and there are a few you must know to properly do your job as a producer.</p><p><strong>RFP and RFQ</strong></p><p>Request For Proposal and Request For Quote are generally sent to vendors that you want to work with on a project. RFPs are usually used when the vendor needs to provide you with ideas and RFQs are usually used for projects you have the concept nailed and need someone to tell how much it will cost. I have also seen RFI used in instances when a company wanted more information and back ground on a specific vendor.</p><p><strong>KPI</strong></p><p>Key Performance Indicators are the stats that show how well or how poorly a property (game, website, film, YouTube channel,etc.) is performing. These are statistics that should always be going up in your main promotional window for a property.</p><p><strong>ROI</strong></p><p>Return On Investment is a little more complicated but it generally means how much are you getting out of the money you are putting in to a project. As an example, your interactive web experience for a film drove x amount of users to a ticket purchasing site and x tickets were sold — the ROI is how much revenue was generated minus the project budget. A question you will hear often is “what is the ROI on that?” your answer should be something like, “we expect to drive x amount traffic which should result in y sales.” Most times, your answer will be much more complex but you should be prepared with something, should the subject surface.</p><p><strong>IP</strong></p><p>Intellectual Property — a salable idea, character, service, story, etc. As an example, Mickey Mouse, and all the things that go along with him, is an intellectual property. Snapchat is another intellectual property.</p><p><strong>BU or Business Unit</strong></p><p>You will hear this quite a bit when working with or within a very large corporation. In general, a business unit is a section of a company that handles one type of product or IP. As an example, that I have specific experience with, at Disney — the Parks are one Business Unit and the Studio is another.</p><p><strong>BUM</strong></p><p>Along the same lines, Business Unit Manager is the primary manager of a business unit.</p><p><strong>PM</strong></p><p>Project manager or Product manager — some companies use these titles interchangeably along with Producer. While our skills sets overlap, the focus of these roles varies slightly. Interactive Producer roles usually encompass both project and product management but also add in a creative component.</p><p><strong>Agile</strong></p><p><a href="https://en.wikipedia.org/wiki/Agile_software_development">Agile </a>is a project management methodology that is very popular in Tech and has been for the last few years. It is intended for rapid development and small teams. I suggest learning the principles of the methodology though very, very few companies implement pure agile.</p><p><strong>MVP</strong></p><p><a href="https://en.wikipedia.org/wiki/Minimum_viable_product">Minimum Viable Product</a> is a product development methodology. It generally refers to the smallest set of features and functionality that you can call a product and launch. The idea is that your team iterates on the product while users are engaged and you can get immediate feedback as to what is working and what is not. This method is not recommended for risk averse teams.</p><p><strong>Ask</strong></p><p>This is what the client or Business partner is requesting. You will usually hear something like, “What’s the ask?” It is shorthand verbiage that I generally avoid like the plague.</p><p><strong>Monetize</strong></p><p>How are you going to make the project/product you’re working on make money?</p><p><strong>Evangelize</strong></p><p>Promotion to your peer group or audiences that may be interested. It comes from the word “Evangelical,” as a reference to Christians who proselytize their faith.</p><p>There are many acronyms and catch phrases that I’m missing but the lingo changes regularly. The items above I’ve heard in use for at least four+ years; I may add more over time.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=da96ae1a5116" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Interactive Producing 101: The Quality Assurance Team]]></title>
            <link>https://medium.com/@malindalloyd/interactive-producing-101-the-quality-assurance-team-8cf19615e671?source=rss-329b663b4a1e------2</link>
            <guid isPermaLink="false">https://medium.com/p/8cf19615e671</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[testing]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Malinda Lloyd]]></dc:creator>
            <pubDate>Mon, 20 Jun 2016 16:36:01 GMT</pubDate>
            <atom:updated>2016-06-21T18:02:49.424Z</atom:updated>
            <cc:license>https://creativecommons.org/licenses/by-nd/4.0/</cc:license>
            <content:encoded><![CDATA[<p><em>*Author’s note — This is an introduction to the QA process. It’s not how everyone works and is not comprehensive but is intended to give an overview to help junior producers get acquainted with the basics. Let’s get started!</em></p><p>The Quality Assurance (QA) team at your company is one of the last groups of people to interact with your project before it goes live to the public. They are the last line of defense against a less than optimal User Experience, broken functionality, incorrect links, poor grammar, and other problems. I’m here to tell you that, despite what it might feel like when you get a bug report, they are your best friends.</p><p>You should already be aware of their process and understand the QA team’s reporting methods well BEFORE the testing starts. But, if not, acquaint yourself now!</p><p><strong>The Process</strong></p><p>At this point, you are almost done with your product — you’ve been working closely with the creative and development teams and you’ve shown the QA team what you’re working on, but they haven’t really tested it yet. You think your product is perfect, ready to go live, but then you hand the QA team credentials to the test site and a test plan.</p><p><em>Dun dun dun …</em></p><p>After they have had their allotted time to test, they submit their first round of test results and the bug report seems a mile long and totally bizarre.</p><p><em>Don’t freak out …</em></p><p>It is *<strong>literally</strong>* their job to find anything that could go wrong/look broken/behave strangely, etc. This is what they do. If the QA team found and reported something, you can bet a rando on the web will find it too and <strong>complain</strong>.</p><p>Very calmly read through every bug. Calmly, because sometimes it will seem like the QA team is screwing with you, the reports are so weird and complex.</p><p>If you have a good QA team, they added screenshots to each report with the steps to reproduce the error, and included the OS and browser versions in which the error occurred. If they haven’t, you will spend a lot of time trying to understand what they are reporting.</p><p>Start sorting the bugs into groups based on difficulty level. Below are a few examples for the web but change them as needed according to your project type.</p><ul><li>small = non-functional links; text corrections such as font sizes, spelling errors, spacing errors</li><li>medium = errors with the responsive modes; animation problems</li><li>large = major functionality is not working as expected and may have an effect on the launch date</li></ul><p>Get your development team working on the small, easy fixes while you validate the tougher ones. It’s going to take the most time to track down the root causes of the medium and large bugs, and these are the bugs that could potentially delay your live/launch date.</p><p>If it affects your launch date, it’s ok to freak out a little — but only to yourself. Never, EVER take frustrations out on the QA guys. EVER. Testing is their job and you will never launch on time at the company from that point forward. Your products will get the finest of fine-tooth combs taken to them. This is not meant to say the QA guys are vindictive, they usually care very much about what they do and if you take your frustrations out on them, you need to be shown that they do what they do to make products better.</p><p>Once you and the development team have tracked down and fixed every bug you can, the QA team tests again. They almost always find more bugs — but nothing is ever really finished when working in digital.</p><p>Now it’s time to decide what must be fixed before launch and what can be fixed later. Grind through the “must be fixed” list and get ready to go live.</p><p><strong>But What if I Work Somewhere with No QA Team?</strong></p><p>First of all, YIKES! However, this is the situation at most small to mid-sized digital agencies — tiny budgets and small projects don’t always allow for a QA resource. If you work at a small company with no QA team, always have another producer or a coordinator review your projects. As stated earlier, you have been staring at the project for a long time; you will definitely overlook problems and be overly confident. So get another set of eyes on what you are working on, anyone you can get.</p><p><strong>Why did I say at the beginning that the Quality Assurance team is your best friend?</strong></p><ol><li>They spot all the issues you missed because you have looked at the product every day for X months/weeks/days.</li><li>They make you AND your product look much better than it would have if you had launched when you thought it was ready.</li><li>A good QA team is generally stacked with really awesome people :)</li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8cf19615e671" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Interactive Producing 101: Choosing the Right Development Team]]></title>
            <link>https://medium.com/@malindalloyd/interactive-producing-101-choosing-the-right-development-team-bff1fadd2343?source=rss-329b663b4a1e------2</link>
            <guid isPermaLink="false">https://medium.com/p/bff1fadd2343</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Malinda Lloyd]]></dc:creator>
            <pubDate>Tue, 14 Jun 2016 16:31:02 GMT</pubDate>
            <atom:updated>2016-06-21T18:03:08.678Z</atom:updated>
            <cc:license>https://creativecommons.org/licenses/by-nd/4.0/</cc:license>
            <content:encoded><![CDATA[<p><em>*Author’s note — This is the basic process I’ve used in hiring development teams in the past. It is intended to help junior talent get a grasp of the process within and organization before they get thrown “into the fire” of hiring a development team. Let’s get started!!</em></p><p>You have a project that needs technical experts but don’t have the development resources. If you normally only work with development teams internal to your company, how do you find the right team to fill in the gap?</p><p>Begin by thoroughly evaluating your needs and the resources you have available for parts of the project that are vital but may be tangential to the development. Here are some started questions as examples:</p><ul><li>What is the goal of the project?</li><li>What devices does it need to work on?</li><li>What code base should be used? Do you know?</li><li>Will the creative be completed by your internal team? User Experience?Design? Copy?</li><li>Will the technical experts, internally, be able to assist the team filling in the gaps when they have questions?</li><li>What skills are needed that your internal team cannot fulfill? Code? Deployment? SEO?</li><li>Does the project require a team local to the company? Or can the team be, at least partially, outside your area of the country?</li></ul><p>Depending on the complexity of the project, you will have different questions to ask but once you feel like you have a good grasp of what’s needed, start your research.</p><p>Canvas your business network for recommendations, don’t start with google. Your contacts can be extremely helpful — they may have hired teams for the same purpose and can lead you to the perfect fit for your needs. You may be able to ask for specific technology or skill set based on your evaluation but if not, you can ask your network more generally for recommendations. The results will likely be a mixed bag of single developers up to large scale agencies.</p><p>Start reviewing the capabilities of each company in the pool of recommendations. You will be able to cross a few off the list immediately, if they don’t have the right skills or appear to exceed your budget. If none of the recommended teams seem to fit, then go to your favorite search engine.</p><p>Once you have a few development agencies that might fit your project, start setting up “interviews” with the teams. Give them a broad overview, not the minutiae of the project, and gauge their response. If you are working within an agency, do <em>NOT EVER </em>discuss who your client is until you have a non-disclosure agreement in place. If you are working on the client side, you still need to keep things as confidential as possible. Below are a few basic questions to ask:</p><ul><li>What are the general rates (if they don’t have it listed on their site)?</li><li>What project management methodology do they use? See if it syncs with your own.</li><li>Depending on the scale of the project, you may want to ask what turn around times can be expected.</li></ul><p>Once you have interviewed a few teams and have your choices narrowed down, it’s time to get cost estimates for your project. Most teams will request a requirements document that details the answers to the questions at the beginning of this article, in order to properly scope and estimate costs for you.</p><p>If you didn’t have the companies sign a nondisclosure agreement before the introductory interview, now is the time to have them sign one. To get the estimates, you will be sending company confidential planning and project data to get an estimate and the agreement will insure that you have legal recourse should the information leak.</p><p>Set a specific time for the development team to submit proposals. This is the first step to making sure that those submitting can meet a deadline and a small test of their interest in the project. You will probably receive all proposals within the time-frame you lay out but, cut from your list anyone who doesn’t make your time frame without a request for an extension in advance of the deadline.</p><p>Don’t look at any of the proposals until everyone has submitted, though you should acknowledge receipt of each proposal via email, at the very least. It will take some patience but you want to wait until you can review all of the proposals together. Set aside some time to focus solely on the proposals submitted and go through them one by one in detail. Cut any proposals that are outside your budget and cut any proposals that exceed your timeline without a plan to roll out additional features later.</p><p>Set aside the remaining proposals and review them again the next day, this allows you time to absorb all the points in each document (or set of documents). Once you have your field of development teams narrowed down to a few candidates, share them with your technical lead. Your tech lead should have additional questions and comments on the teams being reviewed. Their feedback is really important and will help guide you in your final decision.</p><p>If you have additional questions, ask them of the development teams now. You should receive replies that fully answer your questions and if you do not, remove that team from your list. If you don’t get a good response now, you won’t in the thick of a project either.</p><p>Any team you are not moving forward with, let them know immediately. The development teams need know their proposal status so they can book their resources on other projects instead of, potentially, under-utilizing their team while they await a response. It’s always a smart move to keep on the friendly side of dev teams — you never know if you may need to hire them later.</p><p>Once you have your final choice, it’s time to write the contract. You should discuss the contract requirements with your legal team and/or manager but the very basic items you need are:</p><ol><li>Detailed deliverables — what will you receive during and at the end of the project?</li><li>Basic project schedule — when will you receive the deliverables?</li><li>Project Team — who is working on the project from both your team and the vendors?</li><li>Your responsibilities — what do you need to deliver to the vendor?</li></ol><p>If you work for a larger company, there is usually a standard contract format and requirements. Use this as your base and adjust as needed to finalize the contracts. If you are working in a small shop, there are many templates available online but you should review them carefully with a legal professional before use.</p><p>Once all the contracts are signed and all the details are finalized, it’s time to get to work!</p><p><em>P.S. I have several development teams I work with regularly (My favorite is </em><a href="http://www.xivic.com/digital-development/"><em>Xivic</em></a><em> in Los Angeles) but if you need additional recommendations, contact me.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bff1fadd2343" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Interactive Producing 101]]></title>
            <link>https://medium.com/@malindalloyd/interactive-producing-101-1779a981ae64?source=rss-329b663b4a1e------2</link>
            <guid isPermaLink="false">https://medium.com/p/1779a981ae64</guid>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[producer]]></category>
            <dc:creator><![CDATA[Malinda Lloyd]]></dc:creator>
            <pubDate>Fri, 03 Jun 2016 19:21:01 GMT</pubDate>
            <atom:updated>2017-05-14T18:45:10.322Z</atom:updated>
            <cc:license>https://creativecommons.org/licenses/by-nd/4.0/</cc:license>
            <content:encoded><![CDATA[<p>I’ve been thinking a lot, recently, about the invaluable knowledge that was imparted to me over my years as a producer/product manager/project manager in the interactive industry and how important it is to me to help other people grow and develop in the same space.</p><p>With that in mind — I’ve been brewing a few topics to discuss with the community and hopefully encourage junior interactive folks to feel confident and be REALLY awesome.</p><p>Let me know if there are any topics you want to me to cover. I can’t promise the series will be updated often, but I’m going to do my best :)</p><p>Series Posts:</p><p><a href="https://medium.com/@malindalloyd/interactive-producing-101-choosing-the-right-development-team-bff1fadd2343#.j3rvemvf0">Interactive Producing 101: Choosing the Right Development Team</a></p><p><a href="https://medium.com/@malindalloyd/interactive-producing-101-the-quality-assurance-team-8cf19615e671#.lxxq3sega">Interactive Producing 101: The Quality Assurance Team</a></p><p><a href="https://medium.com/@malindalloyd/interactive-producing-101-the-lingo-da96ae1a5116">Interactive Producing 101: The Lingo</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1779a981ae64" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>