<?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 Tobi DeVito on Medium]]></title>
        <description><![CDATA[Stories by Tobi DeVito on Medium]]></description>
        <link>https://medium.com/@tdevito?source=rss-327569310b2c------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*u8bMPw-m16vhfb41XYEfwg.jpeg</url>
            <title>Stories by Tobi DeVito on Medium</title>
            <link>https://medium.com/@tdevito?source=rss-327569310b2c------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 18:46:54 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@tdevito/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[A Gen Xer and a Millennial Walk into A Bar…]]></title>
            <link>https://medium.com/@tdevito/a-gen-xer-and-a-millennial-walk-into-a-bar-12fa66bc632e?source=rss-327569310b2c------2</link>
            <guid isPermaLink="false">https://medium.com/p/12fa66bc632e</guid>
            <category><![CDATA[women-in-technology]]></category>
            <category><![CDATA[generation-x]]></category>
            <category><![CDATA[millennials]]></category>
            <category><![CDATA[women-in-tech]]></category>
            <dc:creator><![CDATA[Tobi DeVito]]></dc:creator>
            <pubDate>Fri, 18 Jan 2019 00:09:56 GMT</pubDate>
            <atom:updated>2019-01-20T00:00:20.380Z</atom:updated>
            <content:encoded><![CDATA[<h3>A Gen Xer and a Millennial Walk into a Bar…</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7aS5keQov3_e_5_JI0YXZg.png" /></figure><p>It’s been a good 10 years now that Millennials and Generation X have had to share air in the workplace. Members of both generations have strong opinions of the other: Millennials exclaiming, “They just don’t know how to be happy!” and Gen Xers replying in exasperation, “It’s called <em>humility</em> people!”</p><p>We (<a href="https://www.linkedin.com/in/tobidevito">Tobi DeVito</a>, Product Leader, and <a href="https://www.linkedin.com/in/emilyhomnici">Emily Hom Nici</a>, Interactive Designer) were no different. We met three years ago while working at a large design firm building enterprise-grade digital products and platforms. What began as a voyage through stormy waters of stereotypes and assumptions evolved into smooth sailing in a rich and mutually rewarding sea.</p><p>Truth. In the tech industry today, it’s hard enough for a woman of <em>any</em> generation to squeeze herself into a place at the table without having to battle our younger or older female selves.</p><blockquote><strong>So, we’re sharing our experience with hopes of easing the pain even a <em>little bit </em>for our fellow nerd sisters out there whom are also building, creating, and making cool shit that aims to do things better tomorrow than it’s currently being done today.</strong></blockquote><p>We began to write this piece by each individually identifying three lessons we learned from our time working together. But, when we sat down to review, we realized that we had inspired in each other the exact <em>same</em> things, only we had arrived at them from completely different angles. The following adages have not only made us better at our jobs, but, they’ve made us stronger women in technology as well. And so, we pass them along to you…</p><h3><strong>#1 Don’t mistake curiosity as distrust.</strong></h3><p>Tobi:</p><p>It was from our parents’ demands for conformity that we Gen Xer’s learned that to question The Boss, was to distrust The Boss. Any refusal to meet our elders’ expectations was often conflated with laziness.</p><p>Early on in our relationship, a Monday scrum revealed that Emily had spent the better part of a weekend continuing to explore additional approaches for a dashboard UI design that I had approved on Friday. I was at a loss. <em>Was she questioning my decision?!</em></p><p>As I dug deeper, I learned that Emily didn’t see it as distrusting my authority. She was just exploring. She took it as a chance to learn. And she <em>liked</em> to learn!?</p><blockquote><strong>Millennials are driven to discover the unknown. Their curiosity about EVERYTHING blurs the lines between work and play. And now, so do I!</strong></blockquote><p>Emily:</p><p>In a time when the next great idea might lead to industry disruption, the internet has cultivated Millennials’ curiosity. We are always asking “why?” — However, I was wary of this inclination in the workplace. I was worried that my inquiries would be perceived as a dumb question or I would lose the trust of my team. So, <em>my tendency was to keep these questions and ideas to myself until I knew they were fully baked and bulletproof.</em></p><p>Tobi noticed.</p><p>She would unrelentlessly force me out of my comfort zone (and still does today) and require me to share my thoughts regardless of their fidelity. She taught me the benefit of speaking up early when my gut said there must be a better way to do something.</p><blockquote><strong>I was encouraged to cultivate my curiosity in a way that was respectful and inviting of my peers. Rather than hiding an inspiration until it was ironclad, I collaborated with my team to spark a new idea and improve the work as a whole.</strong></blockquote><h3><strong>#2</strong> <strong>Being confident is more important than being perfect.</strong></h3><p>Tobi:</p><p>Gen Xers were ranked, measured, and compared to meet our parents’ futile pursuit of perfection. Perhaps my own maroon-colored 13th place ribbon in the 1984 Girl Scout’s Olympics serves as a reminder of my own mediocrity. Our struggle with being ordinary persists. And, <em>as those who shaped us retire or pass on, a sorrowful absence of their unrealistic expectations can often lead to malaise and apathy.</em></p><p>Watching Emily embrace opportunity no matter how daunting with arms wide open took my breath away. It was as if she wasn’t afraid to try anything. She knew she had the talent and thirst to slay.</p><blockquote>Working closely with this bolder generation has gifted me confidence to turn a blind eye to self doubt. I publish pieces that open my ideas up to critique. I speak publicly about lessons learned from my own mistakes. And most significantly, I say “no” to opportunities that will not bring learning or joy.</blockquote><p>Emily:</p><p>My upbringing had convinced me that if I always did my best and worked hard to continually improve my skills, people would notice and encourage me. While, I knew that not <em>every</em> supervisor’s primary goal was to nurture me, I was not prepared for the moment that I faced my first challenging superior. Nothing I did was “right”. No matter how much blood and tears I put into the work, it still fell on deaf ears. Being wrong so many times killed my self esteem.<em> Striving for perfection had failed.</em></p><p>This is when Tobi taught me the value of being confident over perfect. I’d watch her go into client meetings and effortlessly corral the attention of unfocused stakeholders as they asked multiple nebulous questions. She’d initiate tactical moves for the future of the product and smoothly convince every last stakeholder (including the product team) to get behind them. She’d do so confidently and in the exact moments when we really needed someone to herd us all in the right direction.</p><p>While convicted in her leadership decisions, she’d freely admit when her choices were wrong. Watching her willingness to abdicate herself and swallow any pride for the benefit of the product was eye-opening for me (and luckily, she was right 99% of the time). Tobi’s actions taught me not only how to talk the talk, but also that the only way to be confident is to let go of “perfect”.</p><blockquote>Yes, you may make a mistake and have to backtrack, but persevering and moving forward after a misstep will grow a person’s character much more than attempting to never misstep. Go in strong and unapologetically (but respectfully, of course).</blockquote><h3><strong>#3 Careers paths are vertical <em>and</em> horizontal.</strong></h3><p>Tobi:</p><p>Those of us born before video killed the radio star have a deep-rooted respect for paying our dues in the workplace. Thus, we often make the mistake of viewing our relationships with Millennials as a hierarchy. <em>Since we’ve warmed the chair longer, we mistakenly believe we have </em>much<em> to teach and </em>little<em> to learn from our younger colleagues.</em></p><p>When we first started working together, Emily was a Junior Designer. It’s often customary at design firms for a Product Lead to only work directly with a Creative Director. As Emily took on more and more ownership for the product design system, instead of wasting time waiting for the time-constrained Creative Director’s attention, she came to me directly for answers. While, at first aghast, I soon stepped off my artificial pedestal constructed of only a title and ego.</p><p>Working directly with Emily allowed me to see what I stood to learn — best in breed interactive design. I kid you not, everything this girl touches, from cryptocurrency UIs to enterprise digital platforms, oozes with user empathy, visual aesthetics, and intuitive functionality. Partnering with Emily may not get me to the next title in the hierarchy. But, boy, do I now have a better eye for effective product design because of her.</p><blockquote><strong>The Millennial passion laughs in the face of a vertical work path. They embrace a chance to learn, collaborate, and grow from whichever direction it comes, the C-suite or the new batch of interns.</strong></blockquote><p>Emily:</p><p>To fulfill the Millennial mantra “you can achieve whatever you set your mind to,” I believed in working hard and leveling up in the the invisible rankings amongst coworkers (to get that <em>real</em> trophy). <em>While hard work is fundamental to the job, I have learned that it is only one dimension to creating a successful and meaningful career.</em></p><p>Tobi taught me the significance of helping others around you win. By watching Tobi lead her teams, I saw the influential connections she made with her coworkers. She always takes the time to help her peers succeed or standout without hesitation or ego. Being a recipient of her altruism, I have felt firsthand how influential this connection can be — it has helped transform my definition of a “successful” career into one that has a much deeper impact.</p><blockquote>Investing in others may not directly contribute to a climb up a career ladder. However, the deep-relationships and progress create a significant net-positive impact on teams, the work, and people around you.</blockquote><p>I now understand that this aspect of leadership adds breadth, which can be so much more meaningful and impactful on a career.</p><h3><strong>#4 Always order the third drink.</strong></h3><p>…Or cup of coffee, or dessert. Whatever it takes to keep the conversation going between women across generations. We often retreat to our own familiar circles, rarely venturing into the experiences of people older or younger than us. However, technology is driving change in the world at such a rapid pace, we all need as many diverse inputs as possible — older and newer.</p><p>We both feel so lucky to have learned (and continue to learn) so much from each other.</p><p>Our experience from working together has opened new channels of learning and has taught us to broaden our expectations of each other’s generations. We hope to inspire you to do the same.</p><p><em>This article was co-written with </em><a href="https://medium.com/@ehomnici"><em>Emily Hom-Nici</em></a><em>, who is, by far, one of the most talented ladies in tech I will ever have the pleasure of learning from. And, she can even make a mean Moana costume in a single night!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=12fa66bc632e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Agile at Work Building Stronger Client-Agency Partnerships]]></title>
            <link>https://medium.com/@tdevito/agile-at-work-building-stronger-client-agency-partnerships-9cc1bcd84da4?source=rss-327569310b2c------2</link>
            <guid isPermaLink="false">https://medium.com/p/9cc1bcd84da4</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[scrum-master]]></category>
            <category><![CDATA[agencylife]]></category>
            <category><![CDATA[product-owner]]></category>
            <category><![CDATA[agile-methodology]]></category>
            <dc:creator><![CDATA[Tobi DeVito]]></dc:creator>
            <pubDate>Tue, 08 May 2018 20:31:09 GMT</pubDate>
            <atom:updated>2018-05-10T16:38:46.475Z</atom:updated>
            <content:encoded><![CDATA[<h3>Agile at Work: Building Stronger Client-Agency Partnerships</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AUeT1adoE5JWEdyqNmRo9A.png" /></figure><p>The times, they are a-changin’, and the traditional client-agency model is not immune. As companies continue to build out robust in-house creative and technology teams, the demand for design and marketing agencies to provide low-cost/high-frequency services declines.</p><p><em>The game of scale is over for digital design and marketing agencies.</em></p><p>Brands today are in the business of inspiring people to think differently and change their behavior. Clients need transformative ideas that will enable their brand to break through the noise and congestion of highly saturated, non-differentiated markets. At the same time, agencies must retire the <strong>quantity</strong> plays, and embrace the <strong>quality</strong> plays. They must create brand experiences for their clients that inspire meaningful, valuable connections with customers.</p><p>As an Agile Scrum Master and a Product Owner with a combined 30+ years of industry experience we have seen, time and time again, adopting Agile principles is one of the most successful ways for agencies to partner with clients to deliver differentiated solutions and products to wanting business and consumers.</p><p>Unfortunately, there’s a lot of misconceptions about what “Agile” means, and how to implement it. As Ben Edwards and Sol Sender, founding principals at design and strategy firm <a href="http://edwardssender.com/">Edwards + Sender,</a> recently noted, <a href="https://work.qz.com/1201384/everyone-claims-they-are-following-agile-methods-but-few-actually-do/">“Agile” is bantered around</a> — from Account Execs to Design Directors — as if just <em>saying</em> the word ensures a self-organizing team will iteratively create a user-centric product.</p><p>To help you implement Agile processes in your own agency/client partnership, we’ve compiled the following five key tenets we believe agencies and clients alike must embrace if a product is to have a fighting chance at being developed with Agile principles.</p><p><strong>#1 Find comfort in ambiguity</strong></p><p>Abandoning the traditional service-based model and entering into a solution-based agreement with an agency on an Agile project requires clients (and let’s be honest, Procurement Officers) to embrace the ambiguous. Client stakeholders must understand that they are not buying an off-the-shelf product or service complete with standard activities and deliverables. Rather, they must embrace the concept that their company is entering into a partnership with an agency that will result in a customer-centric solution in order to attain their uniquely defined business objectives.</p><p>This repositioning also puts the onus on agencies to evolve how they sell to clients. The days of landing new work just by responding to a canned RFP are coming to a close.</p><p><em>Sharing case studies, securing client testimonials, developing prototypes, and conducting collaborative workshops are becoming common practices required by agencies to secure Agile projects.</em></p><p>Solution-based engagements are as much (if not more) about approach and alignment than about capabilities and project plans. Yet, in the absence of an agreed-upon scope of deliverables, an Agile project requires agencies and clients to collectively define the Product Vision<em> </em>before a single feature is built.<em> </em>By sitting side-by-side to answer the<em> Why?</em>, <em>For whom?</em>, <em>What?</em>, and <em>How?</em> of the future solution, the product teams and client stakeholders ensure complete understanding, agreement, and clarity between their teams. The Product Vision, not the push towards “Big Reveal,” becomes <a href="https://www.vsapartners.com/ideas/product-vision-beacon-scrum/">the beacon</a>.</p><p><strong>#2 Embrace collaboration</strong></p><p>Client stakeholders may assume that an external group of fully-dedicated staff equates to an extension of their internal design or development departments who exist solely to field requests on demand. At the same time, agencies can be extremely hesitant to “open the kimono” on the inner workings of their creative process, refusing to share and ask for stakeholder input on work that is still in progress.</p><p>Collaboration and respect between and among teams is essential to upholding the value proposition of an Agile project: Rapid development of live code shipped to real users. Clients and agencies must find comfort with the terms of a solution-based agreement as they are quite different from traditional waterfall or service-based projects. Some of the greatest barriers for both sides to embrace can be:</p><ul><li>Attending and giving regularly held presentations of work in progress to solicit and provide constructive feedback.</li><li>Identifying sponsor user testing — including customers — and actually using that feedback to inform feature development.</li><li>Dedicating and incorporating subject matter experts onto the team to contribute critical business and operational insight.</li></ul><p><strong>#3 Believe in User-centered Design</strong></p><p>We’ve talked about how the traditional client-agency model is eroding, and in its place we’re finding that Agile practices allow for a much closer — and fruitful — relationship on both sides. The glue to this relationship is a commonly held belief in building solutions that are designed for the end user. This belief requires a level of openness that can put clients and agencies alike in uncharted territory that feels risky to their reputations and practices.</p><p>Clients must open themselves up to user feedback on work that is still in progress, which could reflect directly on their business and brand. It’s a scary prospect to share unfinished, unpolished work with customers who are being asked to “judge” a product your company has invested in. But for a user-centered approach to have a real impact on the end product, clients must abandon their preconceptions of what their customers need and want, and stay focused on the bigger goal: developing, refining, and delivering the right product.</p><p>In turn, agencies should revise their review cycles to accommodate continuous user input and must have teams in place who are responsive and can design against iterative user feedback.</p><p>Openness pays off. With Agile methods, users actually get what they need out of the product — because it is an informed solution that is designed in part by them. And, with a product that solves their problem, clients often see increased customer usage and repeat adoption, thereby achieving their business objectives.</p><p><strong>#4 Build the Right Team</strong></p><p>Siloes are out, integrated teams are in. Clients are increasingly sophisticated — and aware — of how agencies are structured and how they approach staffing. A significant value of an Agile project is a dedicated, multidisciplinary team. So, agencies must ensure the right team mix for the work at hand.</p><p>Below is a checklist of product team “must haves” that clients can use to confirm their agency partner is delivering the best possible team mix to deliver on the solution at hand:</p><ul><li><strong>A dedicated team. </strong>Agencies can be, and at times are, best served by swapping out talent on an Agile project. But, time is money and that money should be dedicated to team activities, not agency inefficiencies. These exchanges can have little to no negative impact on the work if the agency invests in proper on- and off-boarding practices. However, agencies must ensure that moves on the team do not come at the client’s expense.</li><li><strong>Disciplinary expertise. </strong>Different stages of a product life cycle will demand different skills. In the time leading up to the first release, a team may require a more visual Creative Director to help define the design language of the product or a Data Architect to construct the database model. However, once the product is in the hands of users, an Experience Designer and server-side Engineer maybe a better fit to iterate upon the foundation established by their colleagues. In fact, one of the greatest benefits of partnering with an agency on an Agile project is the depth and breadth of their talent bench across disciplines and expertise.</li><li><strong>Bigger is not better. </strong>Padding an Agile team with dedicated hyper-specialized roles is a surefire way to replicate the traditional, siloed agency model you’re trying to avoid. Instead, realize that while you need to match the right talent with the needs of the product, a large team full of experts isn’t required.<strong> </strong>Smaller, focused product teams composed of the essential roles allow an agency to quickly and cohesively build the type of interdisciplinary expertise that makes Agile teams hum — designers that code, UXs that write copy, engineers that order donuts. This also allows a dedicated group to dig deep into the client’s business, market, and industry to truly understand the issues at hand.</li><li><strong>Co-location is key.</strong> Co-location has been shown over and over again to be critical in ensuring team efficiency, self-organization, and productivity.<strong> </strong>We both have seen a significant payoff in investing in keeping the majority of a product team seated in the same office, ideally at the same table. Sourcing staff from several office locations is fine, so long as there is a clear plan that is transparent to the client on how the agency envisions bringing that team together, physically, in one space on a regular basis.</li></ul><p><strong>#5 Invest in Strong Product Leadership</strong></p><p>The continuous and close collaboration between client and agency partners can at times feel chaotic in an Agile environment. Agile project teams are inherently self-organizing, so it can easily appear as though no one is in control or, more importantly, managing the project risk. This is not at all the case in practice. Traditional project management and leadership tasks are in fact distributed across three roles: the Scrum Master, Product Owner, and Client Product Leads. Combined, this de facto leadership group ensures that the solution is being successfully delivered against the Product Vision and that risk is appropriately monitored.</p><ul><li><strong>Agency Scrum Masters protect the team.</strong> Scrum Masters often feels like an air traffic controller who helps the team navigate the daily challenges of a project without getting in the way of the team and their process. Agency Scrum Masters monitor for potential blockers and team progress, while also anticipating their needs on a daily basis. That’s right, <em>daily!</em> Nothing can slip past a good Scrum Master’s radar. Because of this close relationship with the team, Scrum Masters can bring awareness to productivity challenges and potential risks to the project at the team level.</li><li><strong>Agency Product Owners (POs) protect the Product Vision</strong>. The best Product Owners expertly translate the Product Vision at multiple altitudes to ensure that the client and product team remain on point. This is achieved by translating stakeholder requests, defining appropriate goals, and prioritizing the roadmap to ensure a focused delivery of the Product Vision. Moreover, the PO manages the continuous feedback loop informed by internal stakeholders, external stakeholders, and users. A strong PO can gracefully juggle between the needs of the team, users, product, and client with equal attention, never wavering from the beacon that is the Product Vision.</li><li><strong>Client Product Leads protect the business objective. </strong>The client lead completes the trifecta of Agile leadership. A strong client lead needs to be empowered to make decisions in service of the Product Vision and be able to act without obstruction.Successful client leads are empowered by their organization to make on-the-spot product decisions, prioritize without extraneous approvals, and have symbiotic relationships with agency Product Owners. Confidence and trust is key. The second client leads defer to “others” (specifically upper management) in order to make product-related decisions, the leadership team is instantly weakened. Thus, strong client leads are enabled by their own companies, engaged with the agency team, and equally invested in reaching the Product Vision as the agency-side PO.</li></ul><p>As the service-based model becomes a thing of the past, we encourage those in our industry to embrace the possibilities of a solution-based approach. If agencies and clients alike are willing to commit to these key tenets of Agile agency product team success, their partnerships will be uniquely poised to build innovative digital solutions that solve client’s business problems and meet customer’s needs.</p><p><em>This article was co-written with </em><a href="https://www.linkedin.com/in/meredith-neistadt-8ba15625/"><em>Meredith Neistadt,</em></a><em> an </em>extraordinary<em> Project Manager and Scrum Master here at </em><a href="https://www.vsapartners.com/"><em>VSA Partners</em></a><em>, where this article originally was published.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9cc1bcd84da4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Role for Women [and Men] in the Workplace]]></title>
            <link>https://medium.com/@tdevito/the-role-for-women-and-men-in-the-workplace-927a3b8ef260?source=rss-327569310b2c------2</link>
            <guid isPermaLink="false">https://medium.com/p/927a3b8ef260</guid>
            <category><![CDATA[womens-history-month]]></category>
            <category><![CDATA[women-in-the-workplace]]></category>
            <category><![CDATA[women-in-tech]]></category>
            <category><![CDATA[diversity-in-tech]]></category>
            <category><![CDATA[workplace-diversity]]></category>
            <dc:creator><![CDATA[Tobi DeVito]]></dc:creator>
            <pubDate>Sat, 31 Mar 2018 11:25:31 GMT</pubDate>
            <atom:updated>2018-04-09T18:59:24.268Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*R0Tj3XFgQ4onFiXuAL5aNQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*VUI9RU5LU3YfRuOpZSHNhw.png" /></figure><p>Gender bias is everywhere. In the entertainment industry. In the advertising industry. In the technology industry. In the [you name it, it’s got its shit] industry. It’s consuming and arresting.</p><p>But over the past several months, things have started to change. The long-simmering “women’s movement” has gained new momentum from a series of very personal efforts to end the bias against women in the workplace. Women in Hollywood are taking back the narrative with #timesup. Women in the advertising industry are forcing the conversation by calling out offenders on <a href="https://www.instagram.com/stories/dietmadisonave/">@dietmadisonave</a>. <a href="https://www.susanjfowler.com/blog/2017/2/19/reflecting-on-one-very-strange-year-at-uber">Susan Fowler</a> roundhouse kicked open the steel door to cast a gaze at the often loathsome, uninviting-to-the-femalekind technology industry. Really, <em>really</em> brave women (inspired by women of color) are grabbing their guts by the cahungas and taking to social media to own their story with #metoo.</p><p>The reclamation of the personal as political is a throwback to Second-wave feminism that this 1990’s women’s studies minor has been waiting for years to resurface (along with flannel and more Ace of Base). And, as a woman who’s jamming along in a 20ish-year career in and around tech, I’ve had the pleasure of learning a thing or two from some amazing female and male mentors and peers, all of whom own the title of <strong>feminist</strong>[1].</p><p>Thus, as Women’s History month comes to a close, I’m making my personal story political.</p><p>The following are the top three ways I choose to define my role as a woman in the workplace, and still be [pretty f-ing] proud of myself in the morning [2]:</p><p><strong>#1 Stop accepting apologies from any woman that didn’t make a mistake.<br></strong>I am a huge fan of owning my mistakes. I tell my nine-year-old daughter on repeat that one of the best ways to learn is through error. When a woman gives herself room to fail, she is giving herself room to take risks — the kind that change opinions, transform industries, and inspire other women to do the same.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*yjfRbTfVM1qUH7CAMzjuFQ.png" /></figure><p>But because women are so much more likely to own our own mistakes, something else tends to happen: We own others’ mistakes as well. A few weeks ago, a kick-ass female product manager on my team apologized to me for not creating specific documentation on a project. Not only was it not <em>her</em> job to create the document, it wasn’t even her job to <em>ask</em> that the documentation be created! I refused to accept the apology, and so should you.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*uySiX0zGabYUV1Ytw6Ozzw.png" /></figure><p><strong>#2 Don’t be a hater.<br></strong>Many years ago, I began working at a media company. The head of accounts (also a woman, by the way) thought a “great way” to test my skills was to have me manage a woman one year my senior whom they had just passed up promoting — so they could hire me. (This whole sentence just made me throw up in my mouth a little.) The company basically created a catfight… on purpose. My new colleague and I are both fiery Italians, so for about three months, we both bit. It was ugly — the backstabbing, the work sabotage, the pure meanness. But, as I said, we are both fiery Italians. So, at month four, we both realized that we could use our shared passion to succeed, thirst to learn, and love of collaboration for good. After that, we killed it together… and continue to years later. While we are now both in different careers, I still consider her a go-to for advice, an ear, or a shared pitcher of sangria.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*F6I1SCF2EFbSaOFj6qi8cg.png" /></figure><p>Women can be so hard on themselves, which can make it super easy to also be hard on each other just to get ahead. But if we don’t stand up for each other, no one else will. Sure, there are tons of women whose professional style I don’t care for. But I try <em>really</em> hard not to get in their way personally.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*vqH_b880zUxeED3U2BtlrQ.png" /></figure><p><strong>#3 Invite women to the table.<br></strong>I was not lucky enough to have a parent or family friend to open employment-related doors for me right out of college. Yet I was still very lucky: After landing that very first gig with nothing but good interview skills and a slim resume full of volunteer stints, I found women and men who saw my potential, and made room for my [at times frenetic, but always honest] chutzpah.</p><p>Just last week, two male Executive Creative Directors whom I work with often threw my name into the ring for a new opportunity. Although I wasn’t in leadership’s line of sight for the role, those two went on a limb and put me there, making it known they thought I was the right one for the job.</p><p>Women, particularly newer, younger women in the workforce, can struggle to find room to show their true abilities. Instead, their louder, chummier, bro-ier male counterparts may own the limelight much of the time.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*8OE7hxR9bU8D_gbXdIVrNQ.png" /></figure><p>You can be part of the solution. Ask her to co-write that thought leadership piece your CMO requested from you, invite her to the new secret project you are spearheading, put her name forward for unique opportunities you find out about, or ask that she be included in initiatives you know she’d be perfect for.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*PJJCFcfJIkd7eN-6Jbbr1g.png" /></figure><p>There will always be specific, unique moments where we’re focused on empowering women to rip open a can of whoop-ass at work.</p><p>Women’s History month might be over, but every single day, women and men can and <em>should</em> play a role in erasing the bias against women in workplace. We can intentionally choose to take daily interactions and make ongoing choices that even the playing field.</p><p>At some point, the $.20 owed on the dollar for doing the same job as their male counterpart will show up in the paychecks of ladies across the country. And when it does, March can just be called [_______] History month, and resume its rightful place in our minds and hearts: as that slushy third month of the year we can’t wait to slog through.</p><p>[1] <a href="https://www.linkedin.com/in/carol-gipson-2546b85/">Carol Gipson</a> was the first person to take a professional chance on me back in 1998. She saw a light in me that I now see and try to nurture in so many young women entering the workplace today. She also showed me what liking yourself looks like.</p><p>[2] So many amazing lists exist with similar sentiments. My top two these days are: 1) <a href="https://www.3percentmovement.com/sites/default/files/resources/100things_0.pdf"><em>100 Things You Can Do Right Now to Help Drive the 3% Number Upward </em></a>published by the 3% Movement is a great one for my agency friends and 2) <a href="https://www.feministfightclub.com/">Feminist Fight Club</a> was a killer resource for women and men alike looking to kick womanizers in the nuts.</p><p>[3] Have I mentioned my nine-year-old daughter is also <em>Star Wars</em>-obsessed?</p><p>[4] <a href="https://www.census.gov/newsroom/press-releases/2016/cb16-159.html">https://www.census.gov/newsroom/press-releases/2016/cb16-159.html</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=927a3b8ef260" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Product Vision: The Beacon of Scrum]]></title>
            <link>https://medium.com/@tdevito/product-vision-the-beacon-of-scrum-284386f37557?source=rss-327569310b2c------2</link>
            <guid isPermaLink="false">https://medium.com/p/284386f37557</guid>
            <category><![CDATA[scrum-agile]]></category>
            <category><![CDATA[scrum-team-velocity]]></category>
            <category><![CDATA[sprint-planning]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Tobi DeVito]]></dc:creator>
            <pubDate>Tue, 30 Jan 2018 23:09:33 GMT</pubDate>
            <atom:updated>2019-03-03T15:52:07.901Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/720/0*He75mDtKthS7J85A.png" /></figure><p><em>By Tobi DeVito</em></p><p>Agile scrum teams adhere to specific ceremony and guidelines, starting with Sprint 1. However, any successful team — from product developers and stakeholders to executive sponsors — knows that there’s a common beacon: a Product Vision. Before a Sprint 1, teams need to invest time in a Sprint 0, where establishing a Product Vision is one of the main goals. And, while not many will argue against the necessity of establishing a Product Vision, I have encountered my fair share of Sprint 0 haters.</p><p>Most visceral reactions to Sprint 0 (the term I prefer to use for the work an Agile scrum team completes prior to the first day of Sprint 1) are from die-hards that hold tightly to the self-organizing, autonomous, non-hierarchical principles of Agile. They tend to believe all work on a product starts with Sprint 1, including work required by teams to come up with a Product Vision.</p><p>But, at the very start of Sprint 1, scrum teams must be properly armed to measure their progress with <em>velocity</em>. For those who slept through Physics, velocity is speed <em>and </em>direction.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/0*XxPJPaIjP8FmSMWB.png" /></figure><p><em>Speed</em> drives much of an Agile scrum team to quickly iterate toward workable prototypes. But, all of that is for naught in the absence of a Product Vision, or <em>direction</em>.</p><p>A Product Vision allows teams to align on user needs, technology-driven capabilities and business requirements — instilling confidence on the very first day of Sprint 1.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/0*1u6NHgnDW9EVVNfK.jpeg" /></figure><p>When created, documented and agreed upon equally by all parties, the Vision establishes a foundation and common understanding of the purpose of the work by answering the following question:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/0*WmINQUHk25PpwSuE.png" /></figure><p>Design Thinking can be an accelerator to crafting a Product Vision. Begin with gaining a thorough <strong>understanding</strong> of the problem through observation-based insights <em>(Why? </em>and<em>, For whom?)</em>. Then, brainstorm <strong>ideas</strong> about what is going to be built (<em>What?</em>). The inputs from these first two steps are then used to set an initial <strong>plan</strong> (<em>How?</em>).</p><p>While volumes have been written on Design Thinking techniques and methodologies, the following is a highlight of those exercises and approaches I have seen teams use successfully when developing a Product Vision during Sprint 0.</p><p><strong>Step 1: Understand</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/0*ZyAerJuKotip-Iuz.png" /></figure><p>Design Thinking begins with establishing a common agreement of the problem between all involved: stakeholders, product teams and executive sponsors. Teams conduct user interviews, research and discovery to drive consensus on the full breadth of the issue, including the business objectives and target audience.</p><p><em>Why?<br></em>Business objectives explain why the stakeholders are investing in solving this problem for their target audience, and why they are choosing to do so now. They also articulate what a successful outcome of the solution could look like. All objectives should be:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/0*V_qQwgBJvSsj5fJ2.png" /></figure><p><em>For Whom?<br></em>In addition to understanding why a solution is being built, teams must identify the target users and understand their needs. Building an empathy map will help define the solution personas and put the team in the users’ shoes, ultimately positioning the user at the center of the development process. Stakeholders and product teams alike will internalize user pain points, which will allow them to more effectively identify and prioritize product features and requirements in the Product Roadmap.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/0*_9aac8Pfd9btA75F.png" /></figure><p><strong>Step 2: Ideate</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/0*vVw0j9tfV6alX41E.png" /></figure><p>With both business objectives and user personas defined, the second step of a Design Thinking-infused Sprint 0 is to envision what the solution must accomplish to meet the users’ needs — in other words, the solution objectives. In addition, teams can begin to concept what the solution might start to look like.</p><p><em>What?<br></em>While there are many brainstorming methods, in my experience there is no replacement for a good old-fashioned in-person worksession. There’s something about Sharpies, sticky notes, painters’ tape and donuts that really gets the creative juices flowing. That said, I have also seen remote workshops serve as a decent replacement, especially with the litany of collaborative software out there today (e.g., Zoom, WebEx, Mural, Trello, Jira, Slack, Google Docs).</p><p>Regardless of the medium or exercise, teams should work together during this phase to answer the question:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/0*xth3ftJ0r98dfui3.png" /></figure><p>With criteria established, teams can begin to ideate on what the solution itself will look like. They can identify high-level features and/or the potential architecture of the solution. This includes defining frameworks, platforms, data models, tech stacks and QA/test environments and processes.</p><p><strong>Step 3: Plan</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/0*SYMagrpuJw7wPsgg.png" /></figure><p>The last piece of this Product Vision puzzle is the plan that the team will follow to make the vision a reality, the Product Roadmap.</p><p><em>How?<br></em>The Roadmap defines, groups and prioritizes the capabilities the team will build in the solution to meet users’ needs. Capabilities should roll up to the solution objectives and be in support of the larger business goals. They can be grouped in any way that makes sense for the team (e.g., product components, themes or solution objectives).</p><p>However, the groupings themselves should not be prioritized. A Most Viable Product (MVP) is not achieved by building <em>every</em> capability in a single group — such as the entire messaging platform or the full reporting module. Rather, as your team begins to build the Product Roadmap, they should prioritize capabilities <em>across</em> groups, identifying the highest priority for the MVP — for example, a single instance two-way dialogue box or one type of report at initial launch.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/0*V2yy_YPgZ21em_kl.png" /></figure><p><strong>Sprint 1 and beyond</strong></p><p>The Roadmap should be established before any work begins, and be in service of the agreed-upon Product Vision. The Roadmap should also be allowed to grow and change to meet the demands of its users through each release.</p><p>Following this Design Thinking methodology in Sprint 0, teams should be ready to hit the ground running.</p><p><em>As Director, Technology and Product Management Tobi’s career has spanned a variety of disciplines and industries — from leading digital product teams for Fortune 100 clients and executing multi-million dollar media campaigns for leading e-comm retailers, to building CRM databases for national non-profits. At VSA, Tobi delivers bleeding-edge digital experiences for IBM, leveraging Watson and other IBM Cloud and cognitive technologies. Through her broad experience, Tobi has developed the critical skill of nurturing, motivating and empowering teams. In unifying internal and external stakeholders with clearly defined product vision, requirements and purpose, her teams have consistently delivered differentiated, user-centered products across varied platforms, services and tech stacks. Tobi is a Certified Scrum Product Owner and holds a Bachelor’s degree in Philosophy from University of Puget Sound and a Master’s degree in Public Administration from New York University.</em></p><p><em>Tobi can be contacted at </em><a href="http://tdevito@vsapartners.com/"><em>tdevito@vsapartners.com</em></a></p><p>See article on <a href="http://www.vsapartners.com/ideas/product-vision-beacon-scrum/">VSA Partners Blog</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=284386f37557" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Battle of End-Users and Engineers]]></title>
            <link>https://medium.com/@tdevito/the-battle-of-end-users-and-engineers-769a932399f0?source=rss-327569310b2c------2</link>
            <guid isPermaLink="false">https://medium.com/p/769a932399f0</guid>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[user-centered-design]]></category>
            <dc:creator><![CDATA[Tobi DeVito]]></dc:creator>
            <pubDate>Mon, 11 Dec 2017 21:03:12 GMT</pubDate>
            <atom:updated>2017-12-16T14:16:04.686Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/720/0*unft6G_VInwdBZef.jpg" /></figure><p>Today, you’d be hard pressed to find a product shop that <em>doesn’t</em> pride itself on employing User-Centered Design (UCD) to create digital applications and websites. A tremendous amount of rigor is applied — not to mention time and money spent — to ensure sites and apps are built to meet the needs of users, as opposed to business needs or technology requirements. Hours are spent conducting heuristics and interviewing, surveying and observing end users to enable product teams to iteratively design and develop prototypes with the highest level of user satisfaction and adoption.</p><p>However, much too often, the commitment to UCD–envisioning, designing and building features with a user-first attitude — is adhered to in earnest <em>juuuust </em>up until the point of product release. At this time, all bets are off! Launch dates loom… Anxious stakeholders throw down the axe… QA gets squeezed by the day. And, inevitably, product teams quickly revert to traditional software development defect severity and prioritization rankings — rankings that are defined exclusively from a technical and business-driven perspective.</p><p><strong>Redefining severity and priority</strong></p><p>To ensure UCD is adhered to through <em>all phases</em> of product development — including defect ranking and resolution — product teams must begin to adopt broader definitions of severity and priority.</p><p>Let’s start by taking a look at the ISTQB (International Software Testing Qualifications Board) definitions for severity and priority, definitions that are strictly technical or functional in nature:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/0*wp_8ap1vKQCO2DGI.png" /></figure><p>To ensure the user’s needs are present at all times, we must reach beyond just technical functionality and business needs. The following revised UCD-centered definitions keep teams focused on creating experiences that users will love <em>through</em> defect ranking and resolution to launch:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/0*7ZH3abiL8yuNELMM.png" /></figure><p><strong>User Experience Requirements</strong></p><p>Aligning on revised definitions for severity and prioritization is a necessary first step. But in order to keep the product team’s eye on the prize of delighting end users, teams must also gain alignment on what makes for the best ‘user experience.’ To address the full gamut of a user’s experience, a product must meet three distinct types of feature requirements:</p><p><strong>Brand Requirements: </strong><em>How the user experiences the business’s brand in the application.</em></p><p>Brand requirements are critical to a visual expression that is easy, bug-free, and generates user satisfaction, adoption and repeat usage. While brand defects may not <em>prohibit</em> a user from working in the app, poor adherence to brand requirements often leads to inconsistent brand experiences across brand platforms. This causes consumer confusion and overall dissatisfaction, resulting in a decline of usage.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/0*x2o05ogIRAHFRg8M.png" /></figure><p><strong>UX &amp; Visual Design Requirements: </strong><em>How the user functions and behaves (visual and interactive design) in the application.</em></p><p>Visual and functional requirements are key to user success in an application. Like brand, UX and visual design defects might not stop a user from completing a task, but poor UX or challenging design will lead to higher abandonment rates as users become frustrated and confused.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/0*gVUZwv6x4sEl5OYn.png" /></figure><p><strong>Technical Requirements: </strong><em>How the user completes work (technical interaction) in the application.</em></p><p>Technical functionality remains critical to a good product development. If aspects don’t work, users will abandon it. Therefore, technical defects that restrict the ability to use a feature continue to require attention.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/0*c0KUrXQqVuHdIsAU.png" /></figure><p><strong>Revising Ranking Criteria</strong></p><p>When ranking defects, it is common for teams to conflate severity (impact) and priority (importance). However, criteria for these two are very different. The amount of impact a feature has on a user’s experience in the application is not the same as the importance of that feature to the user. Thus, the two criteria must be decoupled when evaluating defects, as both require rigor in assignment independent from the other.</p><p><strong>Severity Criteria<br></strong>The following chart details the existing traditional software (technology and business-driven only) vs. UCD-centered criteria for ranking the severity, or level of impact, of a defect:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/0*FMqX7B6BdZBK7tzD.png" /></figure><p>By including all three types of requirements in the criteria for UCD-centered, teams (and let’s be real, it’s typically developers who apply these rankings. And, at times, with little input from the rest of the product team) are forced to reorient themselves to the user’s needs.</p><p>Thus, when ranking the severity of a bug, the question teams must ask themselves is no longer, <em>“How much does this defect prohibit the feature from working?”</em> Rather, it’s, <em>“How does this defect prohibit the user’s experience–brand, UX &amp; visual design, or technical–of this feature?” </em>This broader definition may even require–gasp!–the designer or UX on the team to help rank severity. (I feel the heaps of garbage being thrown at me from here. I will give you reason to put those rotten tomatoes away in one minute!)</p><p><strong>Priority Criteria<br></strong>In additional to assessing the impact (“severity”) a defect has on a user’s experience, a team must also determine the level of importance (“priority”) of the defect. The following criteria enforces a commitment to UCD in prioritization rankings:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/0*cKRztXA6EdUJwhCk.png" /></figure><p>By positioning the user’s <em>desirability</em> of a defect as the highest priority–above the <em>viability</em>(the traditional criteria for priority) of the defect, the team continues to address the user’s needs first as they plow through defects…even up to the minute of a product launch.</p><p><strong>Severity/Priority Matrix</strong></p><p>With the “severity” and “priority” criteria clearly defined and agreed upon, teams can begin to collectively align on a common understanding of how these two metrics work together.</p><p>Below is a sample matrix of how these two might work together:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/0*VcVMX_Qwc7JcQkVX.png" /></figure><p><strong>The Rollout</strong></p><p>And now, put down those tomatoes. While it is true, no user can actually use a product that is technologically nonfunctional, it does not matter how technologically advanced a product is if no one ever uses it. Making great products <em>requires</em> listening to user needs throughout the cycle of the project… Including defect resolution.</p><p>All this being said, anyone who has actually worked on a product team to develop an app knows, these criteria, are just that, <em>criteria</em>. They are not hard-and-fast rules that teams must live and die on. But they do serve to guide and remind teams that they are building the product for <em>users, </em>not for technology. I have found even if teams I work with just <em>consider</em> that there is an alternative criteria, they are automatically reoriented. I even have one developer who now leads the charge, always being the first to ask the question, “Do users really <em>want</em> this feature?!”</p><p>We must continue to build products that people need, matching the right technology to meet those needs.</p><p><em>As Director, Technology and Product Management Tobi’s career has spanned a variety of disciplines and industries — from leading digital product teams for Fortune 100 clients and executing multi-million dollar media campaigns for leading e-comm retailers, to building CRM databases for national non-profits. At VSA, Tobi delivers bleeding-edge digital experiences for IBM, leveraging Watson and other IBM Cloud and cognitive technologies. Through her broad experience, Tobi has developed the critical skill of nurturing, motivating and empowering teams. In unifying internal and external stakeholders with clearly defined product vision, requirements and purpose, her teams have consistently delivered differentiated, user-centered products across varied platforms, services and tech stacks. Tobi is a Certified Scrum Product Owner and holds a Bachelor’s degree in Philosophy from University of Puget Sound and a Master’s degree in Public Administration from New York University.</em></p><p><em>Tobi can be contacted at </em><a href="http://tdevito@vsapartners.com/"><em>tdevito@vsapartners.com</em></a></p><p>See article on <a href="http://www.vsapartners.com/ideas/battle-end-users-engineers/">VSA Partners Blog</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=769a932399f0" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>