<?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[techattommy - Medium]]></title>
        <description><![CDATA[Discussing Fashion Tech culture, development, innovation and design at Tommy Hilfiger - Medium]]></description>
        <link>https://medium.com/techattommy?source=rss----c57894eeb891---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>techattommy - Medium</title>
            <link>https://medium.com/techattommy?source=rss----c57894eeb891---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 09:07:10 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/techattommy" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Leveraging Quality Metrics: Inspect & Adapt, Measure & Learn]]></title>
            <link>https://medium.com/techattommy/leveraging-quality-metrics-inspect-adapt-measure-learn-19bc22f1d81a?source=rss----c57894eeb891---4</link>
            <guid isPermaLink="false">https://medium.com/p/19bc22f1d81a</guid>
            <category><![CDATA[product]]></category>
            <category><![CDATA[quality-assurance]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[data]]></category>
            <category><![CDATA[product-development]]></category>
            <dc:creator><![CDATA[Tech At Tommy]]></dc:creator>
            <pubDate>Fri, 19 Jul 2019 12:19:48 GMT</pubDate>
            <atom:updated>2019-07-19T13:08:10.122Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7zKjE0bIN7pzZaU_y5558Q.jpeg" /></figure><p><em>Written by Stephen Evans</em></p><p>The Quality Assurance Team at Tommy exists to inspect, measure and challenge the quality of our e-commerce platforms. We can attest that any product team’s ability to focus on quality is influenced by and dependent on many factors, both internal and external. However, it is generally accepted that the most significant influencing factor is <em>mindset. </em>That is to say, encouraging team members to prioritize, take interest in and ownership of the quality of their product. But how can instilling this mindset be achieved?</p><p>One of the foundational tenets of the Agile Manifesto is to <strong>Inspect &amp; Adapt</strong>. By introducing qualitative and quantitative insights, the team will be empowered to identify positive and negative trends (<strong>inspection</strong>). Next, the team can use this data to implement corrective actions (<strong>adaptation</strong>). Finally, they should evaluate the effectiveness of those improvement actions (further <strong>inspection</strong>), thus continuously improving the effectiveness of the team…<em>and</em> the quality of the product.</p><p>But it’s important to keep this measuring mindset where it belongs. Telling a team: “Start measuring X, Y and Z and we’ll see how you’re really performing,” quickly risks taking away control and ownership, likely leading to resentment, disillusionment and a begrudging attitude towards data. In order to improve the team’s effectiveness, allow the data they generate to belong to them. Let the <em>team</em> collect and interpret it.</p><p>If this advice has peaked your interest, here are a few additional tips for nurturing a culture of inspection, reflection and adaptation.</p><h3>1. Start By Asking What Hurts The Most</h3><p>Even if the answer to the question, “What is hurting the team and/or the product the most right now?” isn’t something that can easily be measured, it starts the conversation from the correct <em>team and product-centric</em> place. Your team’s process of inspection should always begin by identifying a purpose and ‘north star’ to work towards.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*FVao-JcXpDDnuMWd.jpeg" /></figure><h3>2. Dig Deeper Into What Hurts Most</h3><p>Usually this comes naturally after answering the previous question, but it’s worth making this step explicit. Rather than choosing a north star on behalf of the team, maintain team ownership of the pain point by questioning and agreeing on the impact <em>together</em>.</p><p>This process might not be so simple. Is the impact anecdotal, a gut feeling or are there already metrics that support the issue’s impact? For example, would you say there are too many defects found in the upper (UAT, Production-Staging) environments? If so, let’s measure this pain and see if data can provide further insights…</p><h3>3. Make The Most Of Best Practice Metrics</h3><p>It’s likely that your team’s pain points are quite common and, as such, can be identified and tracked using existing, standard measurables.</p><p>Are there too many defects found in the upper environments? Is the team saying that bugs are being found<em> too late </em>in the process? If so, maybe measuring MTTD (Mean Time To Detect) can offer solid metrics to work from and consistently track.</p><p>MTTD is just one example, but there are plenty of others: MTTF, velocity predictability, defect count (by story count), defect root cause, etc. are all measurements designed to track the maturity of quality and practice. They also all naturally relate to common issues a team may site as pain points, or something that affects the quality and healthy development of your product.</p><p>By applying these common measurables to an issue or improvement opportunity <em>identified by the team</em>, you’re securing buy-in and greater appreciation for the value of measuring. It’s far better than saying to a team, “Start measuring X, Y and Z and we’ll see how you’re really doing.”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*mOnhLPWgkSqapBbR.jpeg" /></figure><h3>4. Start Small</h3><p>It’s tempting to get carried away with all the things that can be measured, and the promise of having tons of rich information with which to steer the team. However, too much too soon can devalue the data, create frustration and over-burden the team with follow-up actions. (Speaking of which, don’t forget that measuring only provides <em>insight</em>, it doesn’t mean things will get better on their own. It’s what you <em>do</em> with this new stream of data that will determine improvements).</p><p>Indeed, having tons of corrective actions coming from data-driven conclusions can be disruptive to the cadence and balance of the team, ultimately having a negative impact on the development of the product. As such, it’s wise to start small and see how you progress.</p><h3>5. Work With What’s Already There, And Don’t Over-Complicate</h3><p>Applying metics to your pain points may feel daunting, but the great news is that you can start with tools you already have. If you use JIRA, tweak it to provide additional fields that will enable collection of the required data. For example: In which environment was the defect found? What kind of defect is it? What was the root cause of the defect? How long does it take to fix? All of this can be pulled from JIRA pretty easily and at minimal cost to the users of the tool.</p><p>The bottom line: try not to create a significant distinction between the current way of working and what is needed to measure.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Fap5UdJN6ddGZ_XF.jpeg" /></figure><h3>6. Be Consistent</h3><p>Metrics are only useful if they’re collected consistently and correctly, otherwise they provide only partial glimpses of a bigger picture, become anecdotal, or worse still: can be false and misleading. This is another reason to start small, introduce additional metrics slowly and give yourself the bandwidth to…</p><h3>7. Discuss And Adapt</h3><p>When it’s time to discuss the metrics you’ve consistently collected, it’s important not to look at them in isolation. There is a new stream of data, coupled with qualitative interpretations of what the data could mean, plus other mitigating or supporting factors that you may or may not be formally measuring. There are many threads to consider, and you shouldn’t limit the conversation to the numbers.</p><p>Instead, discuss what you’ve collected in the sprint retrospectives alongside opinions, feelings and any other source of potential input. Use this amalgamation to agree on reasonable interpretations and follow-up improvements that can be implemented.</p><h3>8. Don’t Stop!</h3><p>Keep going! It’s a continuous path of improving, adding to, and perhaps even <em>discarding</em> measurements. Continue doing what works and has value, stop doing (or adjust) the things where the value doesn’t warrant the effort needed to collect it. Reflect on how these measurements are helping you to understand your team and product better, and identify the external influences that might be impacting you.</p><p>Happy measuring!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=19bc22f1d81a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/techattommy/leveraging-quality-metrics-inspect-adapt-measure-learn-19bc22f1d81a">Leveraging Quality Metrics: Inspect &amp; Adapt, Measure &amp; Learn</a> was originally published in <a href="https://medium.com/techattommy">techattommy</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Finding Common Ground In Agile Interpretations]]></title>
            <link>https://medium.com/techattommy/finding-common-ground-in-agile-interpretations-e5c113ce5bc5?source=rss----c57894eeb891---4</link>
            <guid isPermaLink="false">https://medium.com/p/e5c113ce5bc5</guid>
            <category><![CDATA[transformation]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[innovation-management]]></category>
            <category><![CDATA[agile-methodology]]></category>
            <category><![CDATA[digital-transformation]]></category>
            <dc:creator><![CDATA[Tech At Tommy]]></dc:creator>
            <pubDate>Thu, 27 Jun 2019 11:54:52 GMT</pubDate>
            <atom:updated>2019-07-08T10:59:23.341Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ADlj5QlIzmlSKsr67Sfgpw.png" /></figure><p><em>Written by Mieke Storms-Wiegel</em></p><p>Tommy’s <strong>Agile Center of Excellence </strong>is rapidly growing. Although we’re only halfway through 2019, our team of Agile coaches has already increased from four to six people. While our expansion is exciting, we also realize that with more people comes a greater need for alignment. For this reason, we organized an off-site meeting with the goal of aligning the team and answering the vital question: <em>what is Agile?</em></p><h3>A Barrage Of New Terms</h3><p>Nowadays we are overrun with buzzwords like “Agile,” “Lean,” “DevOps,” “Scrum” and so on. However, the general understanding of these hot-topic terms is often inaccurate. For example, the terms “scrum” and “Agile” are often seen as one and the same. This is, in reality, a huge misconception! Agile is a <em>mindset</em> that focuses on customer value and adapting to change (amongst other priorities), whereas scrum a <em>framework</em> for how<em> </em>you can actually implement this.</p><p>Since most new teams in Tommy’s <strong>Agile Transformation</strong> are being formed as scrum teams, it’s understandable that many associates are making the assumption that scrum equals Agile. In order to avoid further confusion and misinterpretations, we decided that it was important to stop and align — because only when Agile is perfectly understood <em>within</em> the team, can we spread a clear message across the organization.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OArsqiCwxTb78iN27XtVdg.jpeg" /></figure><h3>Where Is The Room For Interpretation?</h3><p>The Agile mindset is derived from <strong>The Agile Manifesto</strong>, a document that outlines four values supported by twelve principles. This probably sounds like something of a science, with little space for one’s own interpretation. However, we found out that every coach has his or her own unique background and experiences. And although we all have the same <em>knowledge</em> of The Agile Manifesto, we sometimes put our <em>focus</em> on different Agile elements.</p><h3>Getting On The Same Page</h3><p>As a first step in completing our goal, each team member was asked to share their vision of Tommy’s Agile Transformation. We were encouraged to dream about the ultimate success of Tommy’s Agile Transformation, imagining how it would change Tommy Hilfiger as a company.</p><p>We each presented our visions as news items on the cover of a major publication, completely in style with headlines and quotes. It was great to see our ambitions — all big, and varying from becoming the first Fashion Technology company, to applying blockchain, to having the highest employee satisfaction rate due to Tommy’s global implementation of Agile.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3Th8T7mCJVBvn8iTDe5ZUA.png" /></figure><h3>Creating A Shared Definition</h3><p>To achieve these ambitious visions, we of course need our CEO to understand Agile! Therefore, the next task in narrowing our understanding was to create an elevator pitch explaining Agile to our CEO in two or three sentences. After three additional rounds of evaluating, adjusting and optimizing the many definitions, we came to a final, shared definition of Agile at Tommy Hilfiger:</p><blockquote>“Agile is a mindset that enables you to adapt to change quickly and deliver great value to the customer by continuous collaborating and experimenting.”</blockquote><p>There it is! Defining Agile in just one sentence took us half a day (which sounds like an incredibly long time). But by doing this, we took a major step towards establishing our Agile strategy and purpose.</p><p>We look forward to making more strides, and sharing our progress and lessons learned along the way.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e5c113ce5bc5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/techattommy/finding-common-ground-in-agile-interpretations-e5c113ce5bc5">Finding Common Ground In Agile Interpretations</a> was originally published in <a href="https://medium.com/techattommy">techattommy</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The In’s and Out’s of 3D Design]]></title>
            <link>https://medium.com/techattommy/the-ins-and-out-s-of-3d-design-8a3b7690c05c?source=rss----c57894eeb891---4</link>
            <guid isPermaLink="false">https://medium.com/p/8a3b7690c05c</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[3d-design]]></category>
            <category><![CDATA[innovation]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[fashiontech]]></category>
            <dc:creator><![CDATA[Tech At Tommy]]></dc:creator>
            <pubDate>Thu, 27 Jun 2019 09:14:15 GMT</pubDate>
            <atom:updated>2019-07-08T11:02:21.223Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Rlt135Yhu5tSJrId2DlM4g.png" /></figure><p><em>Written by Marlies Reukers</em></p><p>3D Design is at the forefront of Fashion Tech innovation and, as such, is rooting itself in the design teams at Tommy Hilfiger. 3D design refers to the process of digitally 3D-modeling products, garments and other objects. In our industry, fashion design is traditionally done in 2D, meaning flat sketches of new product styles are sent to vendors, a sample is requested and it arrives (on average) three weeks later to be reviewed by the design departments.</p><p>This traditional process demonstrates a vulnerable workflow, due to visual inconsistency, ‘unrestricted’ interpretation for vendors and therefore unnecessary or inaccurate sample requests.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*n8xWaAxLd38wMDW5SZDCKw.png" /></figure><h3>The Benefits of Designing in 3D</h3><p>When working with 3D design tools, there’s no need to request samples for the placement of a pocket, sizing of your artworks, comparisons across the whole size range, or to visualize an all-over print at full scale. And sample necessity aside, this doesn’t even touch on the enormous amount of time saved as a result!</p><p>In short, 3D design creates a more efficient and accurate workflow. Designs sent to vendors are based on <em>facts</em>, all parties have a clear understanding of the desired product, clear visual communication can be provided and designers, pattern makers and fit technicians are able to experiment with new designs on a whole new level!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yEeaQ9Q3oMye92SJoTgYPA.png" /></figure><h3>How is 3D Design Learned?</h3><p>At the moment, 3D design is slowly making its way into the curriculums of fashion design schools. Digital pattern making has been around for some time, but fashion schools are increasingly starting to offer courses on 3D design tools to their students as well. Unfortunately, there is still a lack of knowledge and experience in this field. As it’s such modern technology, few fashion teachers have learned it themselves. Apart from this, the available 3D design tools are developing so quickly that it’s hard to keep up with them, let alone adjust curriculums to facilitate their changes.</p><p>However, in upcoming years, I believe we will see a big change in design graduates regarding their skills and knowledge about 3D design tools. Over the past few years, I’ve already seen a big improvement! With each graduating class, more and more students are showing interest and starting to work with the available software.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xzd_b3gFwr67I3mmPvGEjg.png" /></figure><h3>Preserving Creativity in the Design Process</h3><p>It requires a different approach, and at times a different way of thinking, but working in 3D also opens up the possibility of designing in a completely innovative way. It gives you endless possibilities for visualizing ideas, new constructions or any design you dream up. And, in the end, it’s not about replacing everything physical with 3D digital versions — it’s about having a stronger connection with the product we produce as a company, and the products we all wear on a daily basis. A more hands-on experience with 3D digital as well as 3D <em>physical</em> products can go hand-in-hand for an optimized, future workflow.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Vx7Da292eY2M0XHEQJLUTg.png" /></figure><h3>Design Freedom Gains Accuracy</h3><p>As mentioned before, 3D garments are based on facts, which means the “3D sketch” sent to vendors includes exact patterns, fabric specifications, colours, trims, stitching and any other detailing you can think of. This creates more visual consistency during internal reviews. It also prevents an enormous amount of sample creation during the first stages of the design process. What’s more, 3D design eventually speeds up the workflow since it enables designers to easily access virtual designs and experiments from previous seasons.</p><p>In the future, we might be able to digitize the entire process until final sales. It’s feasible that companies won’t have to produce <em>any</em> products or samples until B2B buyers confirm their orders. Perhaps it’s a coincidence, but so far, some 3D styles in the Digital Showroom are selling better than their ‘photographed’ counterparts.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SQkEqblX3jUxrlbnZGZw_g.png" /></figure><h3>3D Design: The Way Forward</h3><p>I’m convinced 3D Design is the way forward in our industry. Working for a fashion giant like Tommy Hilfiger, I believe it’s our responsibility to create a more sustainable, durable and circular industry. Excitingly, all of this is possible with the help of 3D prototyping in fashion design! Stay tuned to see what’s coming next in this exciting realm of innovation…</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8a3b7690c05c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/techattommy/the-ins-and-out-s-of-3d-design-8a3b7690c05c">The In’s and Out’s of 3D Design</a> was originally published in <a href="https://medium.com/techattommy">techattommy</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How To Optimize Your Meeting Time]]></title>
            <link>https://medium.com/techattommy/how-to-optimize-your-meeting-time-c93b136547f6?source=rss----c57894eeb891---4</link>
            <guid isPermaLink="false">https://medium.com/p/c93b136547f6</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[culture]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[innovation-management]]></category>
            <category><![CDATA[meetings]]></category>
            <dc:creator><![CDATA[Tech At Tommy]]></dc:creator>
            <pubDate>Thu, 27 Jun 2019 09:03:42 GMT</pubDate>
            <atom:updated>2019-07-08T11:04:02.907Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Written by Bartosz Kiera</em></p><p>Let’s start by stating the sometimes not-so obvious:<strong> </strong>meetings are a tool requiring mutual respect; a gathering of people where ideas are exchanged and goals achieved. At least, at Tommy Hilfiger, that’s what they’re <em>supposed</em> to be.</p><p>Nevertheless, you probably find yourself leaving many meetings wondering: Why was I invited to this meeting? Why did we discuss this topic? We talked, argued, discussed — but now what? Why did it take longer then expected?</p><p>Depending on how meetings end, they can feel like a complete waste of time, or, on the contrary, as if you’ve had the best possible conversation. But even when the latter occurs, you must assess: did you achieve tangible progress? To ensure you’re answering ‘yes’ moving forward, here are some tips on optimizing your meeting time, whether you’re an organizer or participant.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*P-3FGPAcg3vSMVeqrA01kg.png" /></figure><h3>Maximize Your Role As An Organizer</h3><p>When you organize a meeting, you need to understand that you are calling on a group of people to individually dedicate time to a topic that matters to you. Their acceptance of your meeting invitation is a gift you must respect rather than misuse. Fortunately, as an organizer, there are a few simple ways to fully value participation in your meeting.</p><blockquote><em>1. Understand your meeting’s goal:</em></blockquote><p>The meeting organizer should establish a clear goal or purpose prior to the meeting. Understanding your objectives can then guide you in setting a proper meeting format. For example, are you going to brainstorm a solution and come up with list of ideas? Do you want a buy-in or decision to be made? Do you want alignment? Do you want to inform people about decisions that have been made, provide progress updates, etc.?</p><p>Each of these goals requires a unique process of facilitation. An organizer must understand this, or they risk approaching every meeting in the same, inefficient manner. If you don’t have experience setting a meeting format that matches your goals, you can always seek help from someone external to the cause. Not only can they assist in structuring the meeting, they can also remain bipartisan and focus on facilitation.</p><blockquote><em>2. Invite the right people and communicate what is expected of them:</em></blockquote><p>After establishing the meeting’s goal, really consider who needs to attend. Map out what you require from each person, from preparation, to decision making to facilitation. Once you’ve established whose participation is actually needed, communicate each person’s role in the meeting, then ensure they have accepted and committed.</p><p>It’s always helpful to send a meeting agenda with the goal clearly stated. This agenda can include what will be discussed, questions that need to be answered and decisions to be made. For longer meetings, section each focus point, set aside break time and list callouts to each person.</p><p>An important final step is to follow-up with participants to ensure they understand what is expected of them, commit to this expectation and lastly, confirm they will come. Sending an invitation email is not enough; you must also confirm it was received and understood.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VdW_SDHtQ_rmicaEv5ET2Q.png" /></figure><blockquote><em>3. Prepare your meeting tools:</em></blockquote><p>The most effective meetings happen between people who are physically and mentally present in the room (close the laptops please). If, however, someone cannot make in any way other than by remote means (video conference, phone call, etc.), make sure these tools are tested and prepared before the meeting starts. Remember the last meeting you were 10 minutes into and still trying to connect one person via video chat? Unprepared tools can waste valuable meeting time.</p><blockquote><em>4. Stick to the allotted time:</em></blockquote><p>Based on the meeting’s goal and format, try to accurately estimate or time-box the meeting. The rule to always keep in mind is: <strong>never run over the scheduled meeting time</strong>. Why? Well, respect is one important reason. You can expect participants’ commitment during the time they agreed to, but beyond that point, you are being disrespectful of their time and taking more than what was consented to. So when your meeting runs long, you cannot assume you will receive the same commitment, focus or productivity.</p><p>How many times have you heard the excuse of someone being late to your meeting because their previous meeting ran late? It’s an organizer’s duty to make sure it ends on time, no matter what. If you have not achieved your goal as you near the end of your scheduled time, use the last 10 minutes to establish a a follow-up plan. And, as the organizer, try to understand why you either didn’t have enough time or if it was spent incorrectly. What went wrong with your estimations? Was there enough preparation both on your side and participants’?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3tx1yW5vkXLFv1NCVmZ0yQ.png" /></figure><h3>Maximize Your Role As A Participant</h3><p>When you say ‘yes’ to joining a meeting, you take on a responsibility towards others who will join. Here’s how to be the best meeting participant:</p><blockquote><em>1. Understand the meeting’s goal:</em></blockquote><p>If this isn’t shared upfront, ask for it. If it’s been shared but you have questions, ask the organizer for clarification. There is nothing more counter-productive than people going into a meeting with different expectations.</p><blockquote><em>2. Embrace your role:</em></blockquote><p>When you accept a meeting, you are agreeing to attend and participate. Make sure you understand the degree of your involvement in preparation, discussion and decision making. You should be able to answer the question: why am I part of this meeting? By coming prepared, you are respecting others’ time and effort.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Xg1FZlGO6rZQvAZMovhfUw.png" /></figure><blockquote><em>3. Prepare your tools:</em></blockquote><p>If you’re connecting to the meeting using remote tools, make sure you have them prepared and connected before the meeting starts. Be respectful of others’ time and don’t make them wait. You should never use the meeting to install what you knew was needed in the first place. I hope you’re noticing a theme behind effective meetings — <strong>respect towards others that manifests itself with preparation and active participation.</strong> If you’re in the room, be <em>fully</em> in the room.</p><blockquote><em>4. Be mindful of ending on time:</em></blockquote><p>If the meeting is running out of time and you have not achieved your goal yet, let the organizer wrap up and schedule a follow-up session. Stop yourself from trying to continue the discussion, as you are taking someone else’s time without their approval. For the follow-up, you can repeat these steps and successfully actualize the meeting’s original objective.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c93b136547f6" width="1" height="1" alt=""><hr><p><a href="https://medium.com/techattommy/how-to-optimize-your-meeting-time-c93b136547f6">How To Optimize Your Meeting Time</a> was originally published in <a href="https://medium.com/techattommy">techattommy</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A Crash Course In Functional Programming (Part I)]]></title>
            <link>https://medium.com/techattommy/a-crash-course-in-functional-programming-part-i-278510cdacac?source=rss----c57894eeb891---4</link>
            <guid isPermaLink="false">https://medium.com/p/278510cdacac</guid>
            <category><![CDATA[functional-programming]]></category>
            <category><![CDATA[programming-languages]]></category>
            <category><![CDATA[development]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Tech At Tommy]]></dc:creator>
            <pubDate>Wed, 26 Jun 2019 11:34:46 GMT</pubDate>
            <atom:updated>2019-07-08T11:05:06.272Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2gJtLYSwd29xUvPRaPEzIQ.jpeg" /></figure><p><em>Written by Jayd Pather</em></p><p><strong>The Development Teams at Tommy Hilfiger are dedicated to knowledge sharing, and this article provides an overview of functional programming. Part I intended for all audiences, including those without an IT background. In the second half of this series, we’ll dive into content intended for developers, which will go into much greater detail and will display real code examples.</strong></p><h3>Let’s Start At The Very Beginning</h3><p>Before we begin discussing functional programming, let’s review the origins of computers and conventional programming. Note: I’ll be using the term “conventional programming” to refer to any language that isn’t functional.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XTJ9eSX18WwDBzptLWigDQ.png" /><figcaption>Alan Turing</figcaption></figure><p>The first computer concept appeared in the 1930’s, when British mathematician Alan Turing conceived the idea. Initially, Turing’s concept was entirely hypothetical, however he would later go on to lead the project to build the first computers during World War II.</p><p>At the same time computer hardware was invented, developers were simultaneously taught how to program it. This is because the hardware designers created an <strong>instruction set</strong>, which defined the operations the computer could perform. These instructions included tasks such as adding two numbers, comparing two numbers, or jumping to a different instruction. A <strong>program</strong> is simply a series of these instructions, and this type of programming is called <strong>machine code</strong>.</p><h3>An Alternative To Machine Code</h3><p>The problem with machine code is that your <em>code</em> often has nothing to do with the <em>content</em> of your program. For example, right now your web browser is showing you a blog article. But, if you were to look at your browser’s machine code, you would see many instructions like adding and comparing, and it would be extremely difficult to figure out the purpose behind the instructions. Needless to say, writing code in this style is very difficult.</p><p>The solution we’ve come up with is creating <strong>high-level programming languages</strong>. Using a high-level language, developers don’t have to think about individual machine instructions like adding or comparing. Your web browser was actually written in a high-level language, so the developers were able to think in terms of real-world concepts, such as downloading files or displaying text and images on the screen.</p><p>Developers use programs called <strong>compilers</strong> to translate our high-level code (the source language) into lower-level machine code (the target language). This translation of our source code creates executable operations, so we can actually run our programs.</p><h3>What Is A Function?</h3><p><strong>Functions</strong> are simply blocks of code that take input and return output. For example, a function might accept two numbers as input, and give their sum as output. It’s important that we make this distinction, seeing them as input and output rather than merely adding two numbers together. Functions actually existed before computers — mathematicians had already conceived of them. However, one mathematician made use of functions in a radically new way.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*sTe4Jx-jU09h6zPvIpN9nA.png" /><figcaption>Alonso Church</figcaption></figure><p>Around the same time that Turing first conceived of computers, American mathematician Alonzo Church wrote a paper about a new concept he called <strong>Lambda Calculus</strong>. Lambda Calculus is a formal system of mathematical logic that defines all mathematics as functions. This includes the parts of mathematics we need for computers: numbers and their operators (+, -, etc.), Boolean values (true/false) and their operators (and, or, not).</p><p>Functional programming was born when Turing decided to study under Church for his PhD. Turing proved that his hypothetical computers were founded on the same principles as Church’s Lambda Calculus. This meant it was possible to compile Lambda Calculus’s into machine code. Essentially, it proved that functional programming could actually be computed by his machine.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*L-AdrddZG-EaQmsVE391cg.png" /><figcaption>Alan Turing and colleagues work on the Ferranti Mark I Computer in 1951</figcaption></figure><h3>What’s next?</h3><p>In Part II, we’ll dive deeper into the pros and cons of Functional Programming. We’ll also look at the differences between functional and conventional languages.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=278510cdacac" width="1" height="1" alt=""><hr><p><a href="https://medium.com/techattommy/a-crash-course-in-functional-programming-part-i-278510cdacac">A Crash Course In Functional Programming (Part I)</a> was originally published in <a href="https://medium.com/techattommy">techattommy</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Takeaways Of Exponential Innovation]]></title>
            <link>https://medium.com/techattommy/takeaways-of-exponential-innovation-9212dcb56c1b?source=rss----c57894eeb891---4</link>
            <guid isPermaLink="false">https://medium.com/p/9212dcb56c1b</guid>
            <category><![CDATA[biohacking]]></category>
            <category><![CDATA[3d-printing]]></category>
            <category><![CDATA[innovation]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[biotechnology]]></category>
            <dc:creator><![CDATA[Tech At Tommy]]></dc:creator>
            <pubDate>Wed, 26 Jun 2019 11:29:31 GMT</pubDate>
            <atom:updated>2019-07-08T11:06:21.359Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Wi7_8kw-kf71hKR9tsCc_Q.png" /></figure><p><em>Written by Delia Lauret</em></p><h3>The Purpose Of Exponential Innovation</h3><p>Singularity University’s Exponential Innovation program is focused on empowering individuals and organizations across the globe to learn, connect and innovate with each other using technology. I attended the program as a representative of Tommy Hilfiger, a leader in innovative Fashion Technology.</p><p>Each day had a different focus: On the first day, we learned about the exponential growth of digital technologies including next-generation AI, digital biology, digital manufacturing, blockchain and extended reality. The second day revolved around mental models, decentralized innovation and rapid prototyping. Finally, on the last day, we discussed corporate transformation and leading exponential change.</p><p>In between lectures, we toured the NASA Ames Research facility. Here we spent time exploring the tech lab, trialing Magic Leap (augmented reality glasses), a 3D printer, a brain-controlled interface and had a conversation with Pepper the robot.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jOBdDvc0xBfT8svWhnNz-g.png" /></figure><h3>From Linear To Exponential Thinking</h3><p>Most of us know about Moore’s Law, which observes the exponential growth in the processing power of computers. However, this exponential growth <em>also</em> applies to digital technology, and that is causing many challenges. For humans, the concept of exponential growth is very difficult to grasp, as we tend to think linearly. Let met give you an easy example: imagine taking 30 linear steps. How far would you get? Maybe 30 meters? Now imagine taking 30 exponential steps (one, two, four, eight and so on). How far would you get in this case? Take a guess, and I’ll share the result at the bottom of this article.</p><p>Exponential growth is linked to the development of technology, but also to the decreasing cost of production. For example, only a few years ago, lab-grown meat cost approximately $300k per pound. Nowadays, that number is down to around $11 per pound, using only 1/10th of the amount of land and 1/10th of water for production. In the near future, the cost of lab-grown meat will equal wholesale costs, and in a few generations, people won’t know the difference if their meat is grown in a lab. Only our generation may find it difficult to adopt these changes, as we’ll remember the prior state of affairs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*7z1yaPSa3icj9j0-2fd4dQ.png" /></figure><h3>Technology Doesn’t Care About Your Feelings</h3><p>In tech and in life, <strong>your mindset is everything</strong>. We all live and see the world through our own biases, but breaking through them can help us ‘unlearn’ narrow perspectives. Also known as ‘shift thinking,’ in order to change what you do, you must first change how you think. Compare it to learning to drive on the other side of the road, or <a href="https://ed.ted.com/featured/bf2mRAfC">riding a backwards bicycle</a>.</p><p>Why is mindset so important? Picture this: nanobots are flowing through your body, <a href="https://futurism.com/kurzweil-by-2030-nanobots-will-flow-throughout-our-bodies">fixing diseases or anomalies</a> before you even get sick. It may sound crazy, but this reality is coming sooner than you might think. So, we can either stick to our biases and ignore the groundbreaking innovation, or shift our mindset to begin thinking about what impact these nanobots could have. Does it mean we will need fewer General Practitioners? Will people potentially become more productive, seeing as the population won’t get sick anymore? Could taking a ‘sick-day’ become a phenomenon of the past? By challenging your beliefs and mindset, you can prepare for upcoming technological developments, benefitting greatly as a result. Because, in the end, technology doesn’t care about your feelings and will continue either way.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*18BGV_fz27Z7ijjWcFI-VA.png" /></figure><h3>Consider Becoming A Bio-Broker</h3><p>One of the program’s most highly debated subjects was digital biology. Sound familiar? The best known example of digital biology is the genome editing program, CRISPR, which is still in it infancy.</p><p>In genome editing, DNA is constructed the same way as computer code (essentially following the format of 0’s and 1’s, but using an 8-letter code). With the help of DNA sequencing, scientists are attempting to ‘debug’ DNA source code to adjust and eliminate diseases. As predicted, with the exponential growth of this technology came rapidly decreasing costs. In 2001, sequencing a human genome cost about $2.7 billion, whereas today an entire DNA sequencing costs $1000.</p><p>In addition to decreasing costs, the quality will also improve over time, thanks to the increasing sample size. The prediction is that one day, DNA sequencing will be done for all newborn babies, and by 2030, predictive healthcare will be available for every baby that is born.</p><p>Scientists are specifically interested in sequencing DNA from the African population, as they are the oldest population in the world and therefore they have the most advanced DNA. However, <strong>this interest raises the question: who is the owner of your DNA?</strong> There is an upcoming market of <a href="https://bit.ly/2ElwzDQ%EF%BB%BF">bio-brokers</a>, who help people take control of their health data by creating a licensing model around their DNA. But that’s not where it ends, DNA can now also be used to store data. Microsoft is working on a such a <a href="https://www.microsoft.com/en-us/research/project/dna-storage/">DNA Storage project</a> at the moment.</p><p>This topic raised a lot of questions surrounding the ethics of DNA sequencing. It’s one thing to adjust DNA to eliminate illness, but quite another to use it to create potential enhancements. Will eliminating diseases make the world more equal, or will this technology create a larger divide between the poor and rich who can afford enhancements? And what about pig/human heart transplants? Is a pig partially human when it gains a human heart? Or is the human with the pig-grown heart not entirely human? What does this mean for human rights legislation?<strong> </strong>In the future, what will it actually mean ‘to be human’? Let me just stop right there.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cAfm7WtAsfAi_iW8roHzSA.png" /></figure><h3>4D Printing Is The New Way To Manufacture Goods</h3><p>In the field of manufacturing, there are innovations in different materials and in production methods. Manufacturers need to become smarter instead of faster (although one usually stands in the way of the other). In the future, engineers will likely turn into constraint managers, because possibilities will be endless.</p><p>Think of 4D printing: there are self-instructing materials that react to water or oxygen to morph. Imagine what this would do to a company like IKEA. You could buy a small box, then at home, expose the content to oxygen so that it grows into your bookstand. Or, think of the development of CT scans with the help of 3D printers, which could immediately produce custom implants while a patient is still on the operating table. With the innovation of 3D printing, it might become possible to start printing human tissue or food. New ways of manufacturing have also been discovered, like <a href="http://madeinspace.us/mission">3D printing in space</a>, which is faster and offers more possibilities.</p><p>Here’s a bit of fun trivia shared by the lecturer: there are counterfeit parts on each commercial airplane in the US, including Air Force 1, due to failing supply chains.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qLnFvXcXsYqokmwhv8K0BQ.png" /></figure><h3>We Are Probably The Last Generation To Die</h3><p>We are close to reaching <strong>longevity escape velocity</strong>, meaning when you are diagnosed with a disease you will die from within a year, the solution to fix that disease will also be found within a year. That being said, an increased lifespan may also result from other unexpected discovery fields, such as Virtual Reality.</p><p>Virtual Reality can help increase the episodic memory of elderly, which is linked to their ability to move, contributing to their health and lifestyle. Or perhaps our increased life longevity will come from 3D printing. What if one day we could start 3D printing human organs, meaning you could drink all you want, because if you damage your liver, you can just print a new one and get it replaced! With exponential innovation, the options decreasing the death rate are truly limitless.</p><p><strong><em>Answer: If you were wondering how far you would get after taking 30 exponential steps… In the last step alone, you would go around the world twenty-six times.</em></strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9212dcb56c1b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/techattommy/takeaways-of-exponential-innovation-9212dcb56c1b">Takeaways Of Exponential Innovation</a> was originally published in <a href="https://medium.com/techattommy">techattommy</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[App Builders Learnings: Ship it Safe]]></title>
            <link>https://medium.com/techattommy/app-builders-learnings-ship-it-safe-7ba6a6a5e654?source=rss----c57894eeb891---4</link>
            <guid isPermaLink="false">https://medium.com/p/7ba6a6a5e654</guid>
            <category><![CDATA[application]]></category>
            <category><![CDATA[mobile-app-development]]></category>
            <category><![CDATA[data]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[development]]></category>
            <dc:creator><![CDATA[Tech At Tommy]]></dc:creator>
            <pubDate>Wed, 26 Jun 2019 11:24:55 GMT</pubDate>
            <atom:updated>2019-07-08T11:12:50.680Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*91Emvs9khnJ1ztCfyB3dpg.jpeg" /></figure><p><em>Written by Justyna Kleczar</em></p><p><strong>On April 29 2019, a number of Tommy’s iOS Community members traveled to Lugano, Switzerland to attend App Builders 2019.</strong></p><p>Let’s start from the beginning. Meet Tommy Hilfiger’s iOS community: Chris, Emre, Alisan, Raj and Justyna. We are a group of iOS enthusiasts working on apps including the PVH (the parent company of Tommy Hilfiger and Calvin Klein) Campus app, VM (Visual Merchandising), eCom in Store and others.</p><p>Despite working on separate projects, we regularly meet to discuss the shared hurdles encountered in our everyday development roles and share input on innovative approaches.</p><p>During one of our weekly knowledge sharing sessions, the idea to attend a conference came up as a good way to gain insight into the newest developments in mobile technology. We enthusiastically looked at various options, and after considering our many points of interest, agreed that <a href="https://appbuilders.ch/">App Builders</a> in Switzerland was the most interesting choice. It is one of the biggest European conferences about mobile technologies, hosted in the picturesque city of Lugano.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VjE3_KZIi4zdJnQ_C9bpVA.png" /></figure><h3>Techniques to Increase Software Security</h3><p>Spanning two days, App Builders was the perfect place to meet other iOS and Android developers, provoke interesting conversations and gain new learning experiences. The schedule was filled with an abundance of high quality talks, but for me, one of the most inspiring was <em>“Ship it Safe”</em> by Guilherme Rambo, a respected speaker and writer for the hugely popular <a href="https://9to5mac.com/">9to5Mac website</a>. Gui’s talk strongly focused on the importance of security and data privacy in software.</p><blockquote>“Here at So &amp; So Inc., we really care about your privacy.” — Everyone</blockquote><p>Haven’t we seen this sentence time and time again on hundreds of websites? And doesn’t it usually appear after a major privacy breach at some company, where millions of passwords were stolen? Security is a complex topic and it is becoming increasingly difficult for companies to prevent such breaches.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*spSqDrkVtSjEC5lBdTEu5Q.png" /></figure><p>Luckily, Guilherme provided tips on what we, as software developers, can do to properly protect our users’ data and what techniques can be implemented to increase the security in our software. The three main topics we need to take into account are:</p><ol><li><strong>DATA: </strong>How to protect our users’ data on their own device and on our servers.</li><li><strong>TRANSPARENCY</strong>: How to ensure that the user is aware about the privacy implications of using your applications, products or features.</li><li><strong>CONTROL</strong>: How to give the users control over their own data — remember that it is their data and not yours.</li></ol><p>Let’s dive into greater detail on each of these topics.</p><h3>Always Protect User Data</h3><p>It is important that software developers take proper measures to protect users data <em>everywhere</em> it might be stored, be it in on the user’s device, on our servers or even in transit. To do so, Gui recommends following these ten golden rules to protect user data.</p><ul><li><strong>Don’t collect data you don’t need. </strong>Remember that we are the ones responsible for the data we collect. Therefore, if we don’t need it, let’s not store it. It’s as simple as that.</li><li><strong>Don’t overwhelm your user by asking for too many permissions, </strong>especially on app startup. Even if your app requires several of them, <em>wait</em> rather than asking for all permissions at launch. Let the user explore your app first, and only once they want to use a feature that requires a certain permission, ask for it then.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qQ-Opi85OUQm102KQWhqMg.png" /></figure><ul><li><strong>Be careful with SDKs. </strong>You should be mindful of what SDKs and libraries you use. Avoid SDKs that might have been downloaded from an insecure source. Since any framework linked to your app has the same access rights as your app, it might (without your knowledge) misuse the permissions for malicious purposes, such as uploading user data to another server.</li><li><strong>Your app = your code. </strong>If you use a library which is misbehaving (for example, crashing the app or using up battery power) and you ship your app including it, it’s still your code, therefore you are the party responsible. The same goes for libraries that might be collecting user data in the background.</li><li><strong>Store user data in iCloud. </strong>CloudKit is great tool for storing user data securely and without giving developers access to the data itself. If the app you are developing is strictly iOS, CloudKit might be a good option to consider for data storage, as it will also take care of authentication (since the user will authenticate via his iCloud account). What does it mean for your app? No login or signup form, no two factor authentication and no taking care of lost passwords. User data protection is fully taken care of by CloudKit as well, so it’s no longer your responsibility.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1mp7PFpfRcnjHKqgK_Vhzw.png" /></figure><ul><li><strong>Process user data on the device. </strong>Think about how much information you want store on the cloud. Does all of it really need to be stored there? Probably not — any data that can be processed on device, should be processed there.</li><li><strong>Protect data on the device. </strong>It’s good to know that you can set Data Protection settings for your app in Xcode. But a little time: complete data protection is set in Xcode by, default so as long as you don’t change it, it should be fine.</li><li><strong>Don’t store sensitive data in your logs. </strong>A recommended logging tool for iOS is os_log, which by default makes any concatenated variables onto your log message appear as “&lt;private&gt;”. The below screenshot is a good example of what a user-data-friendly should look like.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Bl5xnuLuibjVji6b.png" /></figure><ul><li><strong>Backup wisely.</strong> Think about the data your app produces that does not necessarily need to be backed up, such as cache or any data that can be recreated. If it does not need to be backed up, exclude it from the backup.</li><li><strong>Protect your API. </strong>Familiarize yourself with the following technologies when implementing a backend: HTTPS, a protocol used for secure communication. <a href="https://httpsiseasy.com/">HTTPS is easy!</a> ATS (App Transport Security), which enforces HTTPS and will prevent your app from talking to non encrypted services. HTTP Strict Transport Security, which is similar to ATS but for servers. SSL pinning, which prevents your app from talking to a server that is not your own. DeviceCheck if the API is only to be used by an iOS app, so that you can ensure the client that is calling the API is a real iOS device that has your app installed.</li></ul><h3>Provide Usage Transparency</h3><p>Ensure that the user is aware about the privacy implications of using your applications and make it easy for him to understand. Try your best to explain in human language the most important aspects of the privacy policies in your app, such iTunes does below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/892/0*c8roVy7QtoHsuq06.png" /></figure><h3>Give Control Back to Users</h3><p>Give users control over their own data by following these rules:</p><ol><li>Give the user an option to <strong>disable analytics.</strong></li><li>Give users <strong>access to their data </strong>and remember: <strong>it is their data.</strong></li><li>Give users an easy way to <strong>delete their data</strong> from your app.</li></ol><p>These three rules are not so hard to implement, but will make a huge difference to your user.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/464/0*P6q9JZZMi19pF0A1.png" /></figure><p>In sum, following these best practices for security and data protection will definitely help with increasing the security level in your apps. However, as Gui stresses,</p><blockquote>“For me, it takes empathy.”</blockquote><p>Data protection starts with your own attitude. How much do you care about how securely your own data is stored? Probably a lot. If we can feel the same for our users and their privacy, it will help us in designing and implementing better and more secure software.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7ba6a6a5e654" width="1" height="1" alt=""><hr><p><a href="https://medium.com/techattommy/app-builders-learnings-ship-it-safe-7ba6a6a5e654">App Builders Learnings: Ship it Safe</a> was originally published in <a href="https://medium.com/techattommy">techattommy</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Experimenting With No-Code Prototyping]]></title>
            <link>https://medium.com/techattommy/experimenting-with-no-code-prototyping-5d46fd772440?source=rss----c57894eeb891---4</link>
            <guid isPermaLink="false">https://medium.com/p/5d46fd772440</guid>
            <category><![CDATA[development]]></category>
            <category><![CDATA[prototyping]]></category>
            <category><![CDATA[augmented-reality]]></category>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[hackathons]]></category>
            <dc:creator><![CDATA[Tech At Tommy]]></dc:creator>
            <pubDate>Wed, 26 Jun 2019 10:15:09 GMT</pubDate>
            <atom:updated>2019-07-08T11:14:12.512Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5FHDb-MRwXXjtBdvVDS4jg.png" /></figure><p><em>Written by Laura Paulino Periera</em></p><p>Our #NoCode journey started on February 25th, when Lennert de Waal, Systems Engineer at Apple, hosted the Digital Hub’s Downtime (a monthly inspiration series at Tommy Hilfiger). Throughout his presentation, Lennert discussed Augmented Reality in the retail landscape. He shared case studies built with Apple’s A.R. Kit — the kit which (according to Lennert) only required a few lines of code to build a functioning A.R. prototype.</p><p>After Lennert’s presentation, teams were announced for Tommy’s first Hackathon, taking place only two days later in partnership with Apple. The assignment: to<strong> </strong>use<strong> </strong><a href="https://developer.apple.com/videos/play/wwdc2018/808/">Apple’s Augmented Reality Kit</a> to create a product that would enhance the relationship between Tommy Hilfiger and our end-user.</p><p>At the Hackathon, each of the seven, multidisciplinary teams would have only eight hours to come up with an idea and create the best prototype possible. At the end of the day, teams would present their results to an expert jury consisting of PVH Europe CEO, Daniel Grieder; Digital Hub SVP, Anne-Christine Polet; and two senior Apple enterprise representatives. The stakes were high, as the winning team would go on to conduct a Design Sprint with Area52, and thus get the chance to turn their prototype into a reality.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oaceZQ5xrf84zUhareYR9Q.png" /></figure><p>The freshly-announced Hackathon teams were over the moon, for Lennert had just proven that A.R. Kit prototypes could actually look professional after only one day of coding. However, amidst all the excitement, our team suddenly came to a mood-shifting realization: none of us had any iOS development skills.</p><p>Yes, it hurts when you mentally prepare for an A.R. Hackathon, only to realize that you will never be able to build what you just got so excited for. And yes, we did worry about convincing and exciting the Hackathon jury with our only feasible option: a <em>physical</em> prototype. And no, we had no way of turning back.</p><p>So, how did it go? Spoiler alert: <em>our no-code team pulled it off with flying colors</em>. Read on to learn exactly how we did it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sueupR3GLnmSoyOeUr_plQ.png" /></figure><h3>Step 1: Brainstorming</h3><p>We brainstormed several, wild A.R. solutions, but eventually decided to pursue an immersive online shopping experience. In our proposed A.R. experience, users could place a digital Tommy store [i.e. portal] into their physical space [i.e. reality] and walk around the store to explore the latest Tommy collection. While checking out the collection, the user could view products and add them to their online basket. A virtual catwalk would even appear to showcase the products added to their online shopping bag.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Xyq5YbZtJvupGIyj3qqbYA.png" /></figure><h3>Step 2: Storyboarding</h3><p>Once our team agreed upon the concept, we storyboarded a step-by-step visual representation of it. This process required much more effort than anticipated because <a href="https://www.google.com/search?q=tree+swing+what+marketing+suggested&amp;source=lnms&amp;tbm=isch&amp;sa=X&amp;ved=0ahUKEwiEzbuH3PzgAhVR_aQKHY6rB3IQ_AUIDigB&amp;biw=1430&amp;bih=719#imgrc=adf-cRHfeqv90M:">what <em>she</em> thought was not what <em>I </em>meant, which was not what <em>he</em> drew</a>. This was probably the most challenging part of the day, but also the most crucial and valuable, as we finally had a product vision that served as the basis for our prototyping journey.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mTvYKF_uYUiY0L1EjWXj7g.png" /></figure><h3>Step 3: Prototyping</h3><p>Our prototyping kickstarted with a symbolic gift from the Hackathon organizers: a paper, iPad frame with a cut-out screen. This sparked our imagination and before we knew it, someone collected straws, which then sparked 3D assets on a straw, which then sparked a 3D store on straws, and then a runway with a model showcasing items added to the user’s bag.</p><p>This part of the process allowed for so much iteration and we ended up greatly enriching our initial concept.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6DXil3pwRDNCmwSy1QIK7w.png" /></figure><h3>Step 4: Finishing Touches</h3><p>Once we had all the physical elements ready, all we had to do was record a video that combined our many features. We used an iPhone to film everything, using the lens as the users’ eye. It was cool to experience how all the prototyping elements came together in this phase, and also the amount of fun you can have while doing so!</p><p>Ready to see what we came up with? Check out our no-code, physical prototype below!</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FIKZh7ZaIen0%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DIKZh7ZaIen0&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FIKZh7ZaIen0%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/5ad61734624d5ff039b0b5d767e6affa/href">https://medium.com/media/5ad61734624d5ff039b0b5d767e6affa/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5d46fd772440" width="1" height="1" alt=""><hr><p><a href="https://medium.com/techattommy/experimenting-with-no-code-prototyping-5d46fd772440">Experimenting With No-Code Prototyping</a> was originally published in <a href="https://medium.com/techattommy">techattommy</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Recapping MYTOMMY’s React Native HackJam]]></title>
            <link>https://medium.com/techattommy/recapping-mytommys-react-native-hackjam-c5c5db137e3b?source=rss----c57894eeb891---4</link>
            <guid isPermaLink="false">https://medium.com/p/c5c5db137e3b</guid>
            <category><![CDATA[hackathons]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[development]]></category>
            <category><![CDATA[techattommy]]></category>
            <category><![CDATA[react-native]]></category>
            <dc:creator><![CDATA[Tech At Tommy]]></dc:creator>
            <pubDate>Wed, 26 Jun 2019 09:59:38 GMT</pubDate>
            <atom:updated>2019-07-08T11:14:44.919Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lr3wleZAq6LxyQ-Rhsxnzw.jpeg" /></figure><p><em>Written by Merle Stadhouders</em></p><p>In partnership with <a href="https://hackages.io/">Hackages Learning Platform</a>, the MYTOMMY team organized the Digital Hub’s very first Tech Meetup in the form of a HackJam! Fabio Paiva, MYTOMMY’s Tech Lead, previously attended a few HackJams, and was very enthusiastic about the coding challenges assigned, the new skills learned and the interesting people met during the process.</p><p>All in all, this sounded like the perfect opportunity to have a fun evening full of tech, and to meet talented, potential new colleagues. In line with Tommy Hilfiger’s vision of becoming a fashion technology company, we hope to plan another Tech Meetup as soon as possible. But for now, read on to learn all about this successful event.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rkpwMKFVHLU-XYRllHRdvQ.png" /></figure><h3>What Is A HackJam?</h3><p>To organize a HackJam, all you need are burgers, beers and an interesting subject like React Native. Next, invite around 30 enthusiastic developers and you are good to go!</p><p>In all seriousness, much like traditional hackathons, HackJams are coding workshops, typically intended to be very challenging. Fortunately, the Hackages mentors and our own React Native expert, Fabio, were there to help the participants during their paired programming assignment. With a bit of guidance, HackJams allow participants to showcase their development abilities, ideally by completing the assignment in a creative and innovative fashion.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8fN_hi78iQ-s4AQR0opIZw.png" /></figure><h3>Programming With React Native</h3><p>Since the MYTOMMY app is built with React Native (a JavaScript development framework), it was very easy to choose this as the subject of our HackJam. For those unfamiliar with React Native, this framework uses the React library to build native mobile apps for both platforms (iOS and Android) simultaneously. Using React Native, developers can easily create app components with a rich mobile UI. With this Meetup as a first step, we decided to join the React Native community in Amsterdam, where we hope to continue growing and learning from each other moving forward.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zGJyT7TPSE0Kieys4Fl4HQ.png" /></figure><h3>Dividing and Conquering</h3><p>After a first drink and some bites of pizza, the Hackages mentor split the attendees into two groups: developers interested in Apollo/GraphQL and React Native fanatics. The GraphQL teams learned how to create queries to handle a movie list (called Hackflix), while the React Native teams experienced how Flexbox works by copying the Tommy Hilfiger logo (even considering the exact color codes). In the end, all participants worked together and learned how to connect React Native with GraphQL.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jUNo3ub3Oh1z_waarRd2zg.png" /></figure><h3>Learnings For Future Events</h3><p>The event was organized in close collaboration with Talent Acquisition, Digital Hub Communications and the MYTOMMY Product Team. We learned that by joining forces, clearly dividing roles and maintaining strong communication, it is very fun and easy to set up an event! It was also clear that these events show guests the endless possibilities when combining fashion and tech, all while demonstrating Tommy’s potential in this field. And as you may have guessed, we once again proved that developers love pizza, burgers, stickers and beer!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YUSDuAomhM9ihN7QmBYxfQ.png" /></figure><h3>Come One, Come All</h3><p>Are you interested in participating in the next Digital Hub Tech event or Meetup? If so, make sure to keep an eye on this blog, and subscribe to the MYTOMMY news bite. Registration is always free, and all Amsterdam-based techies are welcome to join in on the fun.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*an1pZ42wRMwqAGTZbxlpKA.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c5c5db137e3b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/techattommy/recapping-mytommys-react-native-hackjam-c5c5db137e3b">Recapping MYTOMMY’s React Native HackJam</a> was originally published in <a href="https://medium.com/techattommy">techattommy</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Lessons In Applying Design Thinking]]></title>
            <link>https://medium.com/techattommy/lessons-in-applying-design-thinking-dd4e41d4d02a?source=rss----c57894eeb891---4</link>
            <guid isPermaLink="false">https://medium.com/p/dd4e41d4d02a</guid>
            <category><![CDATA[techattommy]]></category>
            <category><![CDATA[tech-culture]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[innovation]]></category>
            <dc:creator><![CDATA[Tech At Tommy]]></dc:creator>
            <pubDate>Wed, 26 Jun 2019 09:53:24 GMT</pubDate>
            <atom:updated>2019-07-08T11:16:38.222Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_XoKVTHhGGvoZ8RDT9QAKQ.png" /></figure><p><em>Written by Puk de Jong</em></p><p>Employees of Tommy Hilfiger —in both our tech teams and beyond— are encouraged to attend regularly scheduled Design Thinking Fundamentals trainings. Want to know what we’ve learned? Here are our four most important Design Thinking lessons thus far.</p><h3>1. Step Into Your Users’ Shoes</h3><p>As children, we’re all curious. But, over time, we tend to lose that childlike wonder. Maybe it’s because answers are more highly valued than questions in the modern age. Regardless, Design Thinking tells us that it’s important to refocus our attention on asking questions and <a href="https://www.fastcompany.com/3045148/8-habits-of-curious-people">maintaining curiosity</a>.</p><p>The first step in the Design Thinking process is to identify a driving question that inspires you to search for creative solutions. Let’s take the example: “How might we improve the online shopping experience?”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/768/1*HOH34VcJUmpZmCRyJnbq9g.png" /></figure><p>In order to answer this question, you’ll need to get out there and step into the shoes of different users (i.e. consumers). You need to understand: How do they <em>currently</em> experience online shopping? Do they even <em>need</em> a better shopping experience? By being curious and empathizing with the people you talk to (or better, <em>listen</em> to), you’ll discover what your end-users really need.</p><h3>2. There’s No Such Thing As Bad Ideas</h3><p>After defining your user and their needs, it’s time to <a href="https://www.ideou.com/pages/brainstorming">generate ideas</a> that can solve their needs. While you’re working on this, remember to build upon the ideas of others and go for <em>quantity</em> instead of <em>quality</em>. When you truly believe there’s no such thing as bad ideas, you’ll reach real breakthrough ideas.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/768/1*-N71ZGsMJhxShme6g5Imjg.png" /></figure><h3>3. Create Something Ugly</h3><p>Have you ever received this instruction when you were about to start working on an idea? In fact, have you ever heard <em>anyone</em> say this within Tommy? I bet you haven’t, as we tend to produce shining creations backed up by flashy presentations. Because design is what we’re good at, right?</p><p>Design Thinking, on the other hand, teaches us that design is <em>not</em> all about looks, refinement and beauty. At least, not right away. Before adopting anything ‘extra,’ Design Thinking ensures you’re designing for the correct needs of your user. And in order to be certain of this, you’ll need their honest feedback.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3-keulUoQmiSVit_yxaSrQ.png" /></figure><p>But will your user <em>really</em> provide honest and critical feedback when they’re presented with a design that obviously required a lot of time and effort? It’s unlikely that any user is going to criticize this obvious hard work.</p><p>To prevent running into this obstacle, Design Thinking teaches us to create a <em>minimum viable prototype</em> that allows for iterative improvement. By working incrementally, you will leave plenty of space for honest feedback that makes your idea better along the way. Whereas users will find it difficult to come down on a fully finished prototype, addressing a minimum viable prototype allows for open communication, testing and experimenting.</p><blockquote>“Have the mindset of testing to learn, not testing to validate. This is where many people get tripped up; they try to perfect the idea rather than use a low-fidelity prototype to learn from people.”</blockquote><blockquote>— Brendan Boyle, Founder of IDEO Toy Lab</blockquote><h3>4. Tell User Stories That Sell</h3><p>Once you’ve immersed yourself in the daily life of the user and know how to solve their needs, you can tell their story. Walk your audience through their experiences, taking them on the user’s journey. Thanks to the experimentation of your idea with the actual user, you’ll be able to share their experience with real detail. Next, <em>sell</em> your idea by immersing your audience in the user story and the way their pain-points will be solved by using your design. Can you think of any better way to convince your final decision makers?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6YRaK1Ww8guYtsXlFVSVlQ.png" /></figure><p>Design thinking relies on the human ability to be intuitive, recognize patterns and construct ideas that are emotionally meaningful as well as functional. These abilities are necessities in a world where user-first thinking is the norm. To enrich the mindset of the future, Design Thinking is indispensable in the skillset of each Tommy associate.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dd4e41d4d02a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/techattommy/lessons-in-applying-design-thinking-dd4e41d4d02a">Lessons In Applying Design Thinking</a> was originally published in <a href="https://medium.com/techattommy">techattommy</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>