<?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[imagiLabs - Medium]]></title>
        <description><![CDATA[The imagiCharm is a smart accessory that you can customize through code! Learn Python in the imagiLabs app - Medium]]></description>
        <link>https://medium.com/imagilabs?source=rss----cc4dacbcbf16---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>imagiLabs - Medium</title>
            <link>https://medium.com/imagilabs?source=rss----cc4dacbcbf16---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 15:33:50 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/imagilabs" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Reflections from a Startup Founder Who Hasn’t Mastered the Art of Crafting a Catchy Title (yet)]]></title>
            <link>https://medium.com/imagilabs/reflections-from-a-startup-founder-who-hasnt-mastered-the-art-of-crafting-a-catchy-title-yet-79faa9f7269?source=rss----cc4dacbcbf16---4</link>
            <guid isPermaLink="false">https://medium.com/p/79faa9f7269</guid>
            <category><![CDATA[founders]]></category>
            <category><![CDATA[startup-life]]></category>
            <category><![CDATA[founder-stories]]></category>
            <category><![CDATA[impact]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Paula Dozsa]]></dc:creator>
            <pubDate>Mon, 03 May 2021 15:57:54 GMT</pubDate>
            <atom:updated>2021-05-07T10:29:08.490Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0FGKEW1rx9HthYbkJP4ZDQ.png" /></figure><p><strong>“Paula!! how are you doing? 🙂 how is the real world treating you?”</strong></p><p>This is the text I received from Dora, a friend from university, in the fall of 2018. I had graduated a few months earlier and had just moved to Hong Kong for my first full-time job. The real world consisted mostly of me clanking away at a keyboard on the 65th floor of a steel-and-glass office tower, posting pics of my brunches on Instagram, and checking out all of Hong Kong’s rooftop bars. True post-graduate bliss.</p><p>Dora and I knew each other from our time at NYU Abu Dhabi, where we’d taken a few introductory computer science classes together, and where I’d been one of the first to join weSTEM (Women Empowered in STEM), the student group that she and and her classmate Beatrice had co-created. After they graduated, Dora and Beatrice had gone on to co-found imagiLabs, a startup that was building a product to teach girls how to code, and a few days after receiving Dora’s text I joined imagiLabs as well, initially as a part-time iOS developer.</p><p>At the time, my knowledge of startups stemmed mostly from the fictional Pied Piper startup in HBO’s Silicon Valley, and another fictional startup I’d been a part of for a business challenge in my second year of university. Up until that point I’d only experienced working at mega-corporations with thousands of employees. Joining a startup felt like an unconventional path, one that I hadn’t previously thought of pursuing. <strong>At 23, I thought I knew myself pretty well, and that self was someone who craved stability and comfort.</strong> I blame it on my sun sign, Taurus.</p><p>Nevertheless, less than a year after receiving Dora’s text, I bought a one-way ticket to Stockholm to join the founding team. Fast-forward to today, and I’ve now been a part of imagiLabs for about two-and-a-half years, leading the development team. Throughout this time, the imagiLabs team has experienced growing pains, surprises (both good and bad), and great joys. We have moved offices several times and our Slack workspace has seen dozens of employees and interns come and go. Looking back at all we’ve accomplished and thinking ahead to all we have yet to achieve, this period feels like both an eternity and just a blip of time, which I’ve come to learn is exactly how time works in the startup world.</p><p>This may be a cliché, but I’ve gone through a rollercoaster of experiences and emotions, ranging from very high highs to very low lows, from dancing in the streets after receiving great fundraising news, to curling up in bed, burned out, anxiety flooding my brain at every Slack DM. <strong>Everything about startups is a lot. A lot to do. A lot to handle. A lot to be uncertain about. A lot to be responsible for.</strong> Things become very personal very quickly, and I tend to perceive myself as directly responsible for a lot of things, especially when they go wrong.</p><p>I’ve come to accept that I probably won’t become an expert in any one particular thing as part of my work. If acquiring expertise and specialization are what you strive for in a job, you’re not going to find that here. <strong>During my time as a technical founder of our small but very ambitious startup, I’ve learned and done many very different things, some expected, some not.</strong> I joined imagiLabs expecting that I’d be learning more about iOS development, then went on to also lead backend, web, and Android development, and have since found myself heavily involved in all aspects not just of our product, but also of sales, partnerships, recruitment, marketing, and fundraising. I’ve developed and published a mobile app. I’ve interviewed and recruited developers. I’ve created and executed on an influencer marketing strategy. I’ve pitched to investors. I’ve taught our partners how to use our tools to teach coding to girls all over the world. I’ve learned about SEO and how this blog post will apparently make it easier for people to find our website.</p><p>At first I found myself paralyzed by the amount of things I had to learn, unsure how and where to start. I’ve found, however, that with each new challenge, the mental block has eased. I’m now less afraid of jumping in at the deep end. I’m gaining the confidence that I can figure things out. And although I do the best I can, I don’t claim to do these things perfectly. <strong>I used to pride myself in striving for perfection, but I’ve come to realize that <em>done</em> is better than <em>perfect</em>, and that is okay, and that is how I will move forward.</strong></p><p>Joining a startup means embarking on a wild journey. But what I also know now, two-and-a-half years later, is that it’s all worth it. I’ve done outrageous and amazing things with incredible people, things that my 23-year-old self would’ve found completely out of her reach and comfort zone. I feel fulfilled in a way I didn’t think possible, and I’m grateful to have had the privilege and opportunity to embark on this collective exercise in grit, learning to embrace the uncertainty, one Slack message at a time.</p><p><em>As always, thank you to </em><a href="https://medium.com/u/5880401408ea"><em>Melinda Szekeres</em></a><em> for editing my jumble of thoughts into a coherent piece, and pushing me to take a much more reflective and personal stance than I’d initially aimed for.</em></p><p><em>Originally published at </em><a href="https://imagilabs.com/blogs/news/reflections-from-a-startup-founder-who-hasn-t-mastered-the-art-of-crafting-a-catchy-title-yet"><em>https://imagilabs.com</em></a><em> on May 3, 2021.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=79faa9f7269" width="1" height="1" alt=""><hr><p><a href="https://medium.com/imagilabs/reflections-from-a-startup-founder-who-hasnt-mastered-the-art-of-crafting-a-catchy-title-yet-79faa9f7269">Reflections from a Startup Founder Who Hasn’t Mastered the Art of Crafting a Catchy Title (yet)</a> was originally published in <a href="https://medium.com/imagilabs">imagiLabs</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Tech is Still Missing Out on a Critical Talent Pool — Here’s How]]></title>
            <link>https://medium.com/imagilabs/tech-is-still-missing-out-on-a-critical-talent-pool-heres-how-6f77afee2cf?source=rss----cc4dacbcbf16---4</link>
            <guid isPermaLink="false">https://medium.com/p/6f77afee2cf</guid>
            <category><![CDATA[diversity]]></category>
            <category><![CDATA[workplace]]></category>
            <category><![CDATA[accessibility]]></category>
            <category><![CDATA[inclusion]]></category>
            <category><![CDATA[tech]]></category>
            <dc:creator><![CDATA[Amina K]]></dc:creator>
            <pubDate>Thu, 28 Jan 2021 09:53:50 GMT</pubDate>
            <atom:updated>2021-01-28T09:53:50.340Z</atom:updated>
            <content:encoded><![CDATA[<h3>Tech is Still Missing Out on a Critical Talent Pool — Here’s How</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*zCotANdRPyK4o0gw" /><figcaption>Python Code Snippet on Inclusion and Accessibility</figcaption></figure><p>Listening to a podcast episode addressing inclusivity in the workplace, I couldn’t help but reflect back on my own career steps as an aspiring tech professional. I identify as both a programmer and a woman with an invisible disability. As a result of these identities, not only do I have to prove my competence as a woman in a male-dominated industry every day, but I also have to constantly fight for my rights as a person with a disability.</p><p>For me, a prospective job applicant, inclusivity in a workplace is not just another tick on a list of how amazing a certain company is. An inclusive environment became a necessity that — I learned — not many professional settings can provide to people who depend on inclusive policies to perform well and succeed. The lack of diversity and representation of people with disabilities in tech is vast, and my story is just a tiny drop in the ocean. Meanwhile, companies that fail to support people with disabilities <a href="https://www.accenture.com/_acnmedia/PDF-89/Accenture-Disability-Inclusion-Research-Report.pdf#zoom=50">typically underperform financially</a> in comparison to their more supportive peers by missing the unique opportunity to leverage a <a href="https://www.accenture.com/_acnmedia/PDF-89/Accenture-Disability-Inclusion-Research-Report.pdf#zoom=50">critical talent pool</a>.</p><p>The <a href="https://www.bls.gov/news.release/pdf/disabl.pdf">U.S. Bureau of Labor Statistics</a> reported that in 2019, only 19.3% of people with different abilities were employed, compared to 66.3% of persons without a disability. A <a href="https://www.washington.edu/doit/book/export/html/935">National Science Foundation</a> study further shows that scientists and engineers with disabilities experience higher unemployment rates than their counterparts.</p><p>Looking closely at diversity reports of different tech companies, one can find how much work there needs to be done. At LinkedIn, for example, the pool of new-hires in 2016 consisted of only <a href="https://blog.linkedin.com/2016/10/18/linkedin-2016-workforce-diversity-data">42%</a> women and <a href="https://blog.linkedin.com/2016/10/18/linkedin-2016-workforce-diversity-data">3%</a> persons with disabilities. Four years later, these figures have not risen by much at the company. The percentage of women employed at Amazon, Facebook, Apple, Google, and Microsoft still ranges between <a href="https://www.statista.com/chart/4467/female-employees-at-tech-companies/">28 and 42%</a>, and other historically underrepresented minorities can be found in fractions of these numbers.. Google’s workplace, for instance, is made up of just <a href="https://kstatic.googleusercontent.com/files/25badfc6b6d1b33f3b87372ff7545d79261520d821e6ee9a82c4ab2de42a01216be2156bc5a60ae3337ffe7176d90b8b2b3000891ac6e516a650ecebf0e3f866">32%</a> women and <a href="https://kstatic.googleusercontent.com/files/25badfc6b6d1b33f3b87372ff7545d79261520d821e6ee9a82c4ab2de42a01216be2156bc5a60ae3337ffe7176d90b8b2b3000891ac6e516a650ecebf0e3f866">6.1%</a> people with disabilities in 2020.</p><p>When combined with the already-existing gender gap in tech, the disability gap creates an even greater barrier for people like me to enter the field. The reasons vary from <a href="https://www.washington.edu/doit/book/export/html/935">inadequate academic support</a> to <a href="https://www.washington.edu/doit/book/export/html/935">lack of role models</a>, but the main one remains the same: <em>lack of accessibility.</em></p><p>Even before entering the professional sector, university students with disabilities receive <a href="https://nlts2.sri.com/reports/2011_09_02/nlts2_report_2011_09_02_ch2.pdf">less support and feel more excluded</a> than their peers. Organizations and institutions tend to focus on meeting “default” needs. Non-accessible participation leaves many students with disabilities out of early career opportunities, resulting in a greater employment gap in workplaces.</p><p>Consider, for instance, the technical interview processes that most tech jobs require. The vast majority of workplaces around the world are unfamiliar with offering special accommodations — be it technology assistance for a phone screening interview or a distraction-free venue for an onsite interview. For example, Candidate A requires keyboard assistance for expressing their communication better due to a disability. The interviewer, if unable to meet Candidate A’s needs for accommodation, fails to judge Candidate A’s skills objectively and make the most accurate conclusion, thereby rejecting this applicant from the pool. Candidate B, on the other hand, does not require any accommodations and therefore does fit the “default” criteria of the selection process. This allowed Candidate B to have a greater chance of being evaluated objectively and getting recruited.</p><p>When it comes to accommodations for physical disabilities, <a href="https://www.researchgate.net/publication/316628595_Employment_Discrimination_Against_Persons_with_Disabilities_Evidence_from_Matched_Pair_Testing">research</a> shows that candidates with a disability were “only 27% as likely to receive a job offer or [advance] in the hiring process” compared to other <em>equally</em> qualified counterparts.</p><p>Without accommodations, it becomes difficult to succeed in an environment that favors only one way of participation. Disclosing a disability and asking for accommodation, in this case, becomes a challenging task. Moreover, many hiring managers are unfamiliar with due procedures or are reluctant to follow them regardless of the <a href="https://www.dol.gov/general/topic/disability/ada#:~:text=The%20Americans%20with%20Disabilities%20Act,local%20government&#39;%20programs%20and%20services.">legal implications</a> in some countries. In the worst cases, these employee candidates are already met with <a href="https://link.springer.com/article/10.1007/s10869-018-9602-5">implicit prejudice and covert discrimination</a>. As a result, the process that is supposed to be a medium to show a candidate’s best qualities becomes a place of “<em>mismatched interaction”</em>, the term introduced by Kat Holmes in her book “<a href="https://mitpress.mit.edu/books/mismatch">Mismatch How Inclusion Shapes Design</a>”, and potential social rejection.</p><p>If this exclusion cycle is not disrupted in its early stages of development, it becomes almost impossible to break it. Consequently, people who are already underrepresented in the field cannot enter it if the only way to do so is not accessible to them. We must make the process of getting in more accessible; otherwise, the gap will never be reduced and mismatched workplace interactions will continue to thrive.</p><p>An obvious way to improve accessibility is to first address the root of the issue: the homogeneity of the tech industry. Previous articles on the imagiLabs blog, such as <a href="https://medium.com/imagilabs/how-i-became-a-programmer-while-not-looking-like-one-33c330c69a2b">How I Became a Programmer While Not Looking Like One</a> and <a href="https://imagilabs.com/blogs/news/why-gender-equality-in-tech-is-a-prerequisite-for-gender-equality-in-society">Why Gender Equality in Tech is a Prerequisite for Gender Equality in Society</a>, shed light on the process of breaking the industry’s “defaults” and increasing diversity in tech. Organizations and educational institutions must first question the accessibility of their recruitment practices and then actively support a range of ways for people to show up and participate, fostering a culture of inclusion and belonging. Embracing individual experiences without expecting them to fit a certain template is the fastest way to embrace authenticity and hear voices that were too often excluded from the field before.</p><p>In the past few years, more and more people have started to share their personal experiences and hold the corporate world accountable for its lacking diversity of representation. Accessibility advocate Meenakshi Das, for example, recently <a href="https://rudermanfoundation.org/link20_blog/interning-at-a-top-tech-company-as-a-person-with-a-disability/">shared</a> her sentiments about having a disability and becoming a software engineer at Microsoft, “Growing up watching television and movies, they always portrayed successful people who worked at big companies as able-bodied, and who spoke extremely fluently…Naturally, I never thought I would fit in and did not see myself as working at big corporations. I didn’t think I would be accommodated or accepted.”</p><p>The number of organizations supporting underrepresented groups in tech has also been increasing. <a href="https://www.limeconnect.com/#who-we-are"><em>Lime Connect</em></a>, the largest not-for-profit network for young professionals, provides tech opportunities for students with disabilities. Another leading nonprofit resource for business disability inclusion, <a href="https://disabilityin.org/who-we-are/about/"><em>Disability:IN</em></a><em>, </em>provides opportunities for people with disabilities across partner organizations.</p><p>From people speaking out about different workplace experiences to organizations offering a wide range of programs and accommodations for people with disabilities, the power dynamic starts to slowly change towards diversity, equity, and inclusion. Although there is still a long way to closing the disability gap in tech, educational institutions and corporate organizations must continue to create inclusive workspaces. The faster we as a society drop our expectations of having only one way of contributing to the field, the more professionals we will see emerging and bringing their diverse perspectives to build a better world, for all of us.</p><p>Experiencing this organizational shift first-hand, I feel empowered to own my identity and share my story. Interning at imagiLabs — a company with a mission to create diversity in the world of technology — has given me the opportunity to grow as a person and develop professionally, all while embracing who I already am.</p><p><em>This post was written by Amina Kobenova, former Creative Content and Coding Developer and incoming iOS Development Intern at imagiLabs.</em></p><p><em>Originally published at </em><a href="https://imagilabs.com/blogs/news/inclusivity-in-the-workplace"><em>https://imagilabs.com</em></a><em> on January 26, 2021.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6f77afee2cf" width="1" height="1" alt=""><hr><p><a href="https://medium.com/imagilabs/tech-is-still-missing-out-on-a-critical-talent-pool-heres-how-6f77afee2cf">Tech is Still Missing Out on a Critical Talent Pool — Here’s How</a> was originally published in <a href="https://medium.com/imagilabs">imagiLabs</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A startup year full of just-in-time learning]]></title>
            <link>https://medium.com/imagilabs/a-startup-year-full-of-just-in-time-learning-bed22d86ac93?source=rss----cc4dacbcbf16---4</link>
            <guid isPermaLink="false">https://medium.com/p/bed22d86ac93</guid>
            <category><![CDATA[founder-stories]]></category>
            <category><![CDATA[startup-lessons]]></category>
            <category><![CDATA[women-in-tech]]></category>
            <category><![CDATA[year-in-review]]></category>
            <category><![CDATA[female-founders]]></category>
            <dc:creator><![CDATA[Dora Palfi]]></dc:creator>
            <pubDate>Thu, 31 Dec 2020 12:03:42 GMT</pubDate>
            <atom:updated>2021-01-29T22:22:39.486Z</atom:updated>
            <content:encoded><![CDATA[<blockquote>“I feel like every single lesson you learn in a startup is just in time or sometimes just after you needed to know it.” Melanie Parkins, the founder of Canva, said this in a recent <a href="https://mastersofscale.com/melanie-perkins/">episode</a> of Masters of Scale, and this really spoke to me.</blockquote><p>Two and a half years after founding <a href="https://imagilabs.com/">imagiLabs </a>I think one of the most important lessons I have learnt is that there is nothing we can’t learn, if we really need and want to!</p><p>I wrote<a href="https://medium.com/imagilabs/a-startup-year-in-review-the-founding-story-continued-82e134d6c927"> my first annual review</a> of our startup life last year, focusing on the idea that every time we commit to doing a certain task we say no to a thousand others we could have accomplished, reviewing what were the things we did commit to in 2019.</p><p>This year, for the second annual review, I am highlighting a few important things I learnt — <strong>just-in-time (and sometimes a little later than I needed to know them). </strong>It is again a brutally transparent account of the last 12 months, which in 2020 included launching our product in the midst of a pandemic, and of course countless downs (financial struggles, production delays) but even more ups (happy customers, growing business).</p><p>I started <strong>January</strong> with taking a full week off (for the first time since starting imagiLabs) and so the first lesson of 2020 was that going on vacation is not only something we should want to do but also something we need. It is an incredible opportunity to step back and put things into perspective, to realize our day-to-day problems with the business might be smaller than we think. And for any founder who thinks they always need to be around to help and fix problems as they emerge it is an important lesson to learn that things actually get done without us (sometimes even faster than if we were around)!</p><p>While I took my holiday, <a href="https://medium.com/@beatricius">Beatrice</a> was visiting our manufacturing partner in China, reviewing the pre-production units of the imagiCharms. In January we didn’t just receive news about COVID (☹️ ) but also 60 pre-production units of the imagiCharms in our Stockholm office, a huge milestone for us!</p><figure><img alt="A box of imagiCharms and happy founders" src="https://cdn-images-1.medium.com/max/1024/0*NCYMUK52LuzoIILY" /><figcaption>Our pre production units arrived in January!</figcaption></figure><p>That being said, our already shaky financials combined with the learning that our production would be delayed (due to COVID and its impact in China already early in the year) led to us co-founders deciding not to take salary for two months. But as I learnt from Paula, <a href="https://medium.com/@pauladozsa/my-thoughts-on-knowyourworth-after-an-80-pay-cut-4dd448039f">not having a salary does not define your worth</a>.</p><p>In <strong>February</strong> I learnt to pitch without investor/startup lingo, as I was on-set, participating in the Hungarian edition of Shark Tank. It really is true, the shorter your pitch the more time you need to put into crafting it. Simultaneously, thanks to being one of this year’s <a href="https://www.cartierwomensinitiative.com/fellow/dora-palfi">Cartier Women’s Initiative</a> Fellows, I was taking an intense online course on financial modelling. I assume that for anyone with a business background it might be shocking that I really just started to understand the ins and outs of our financial statements and cash flow projections a year and a half after starting a company, but I would say it happened just in time.</p><p>In <strong>March</strong> I continued learning about all the legal and administrative work that comes with founding a company, as we held our first annual general meeting. Although not the type of work that motivated me to start a company, one thing I can say is that being as passionate about imagiLabs as I am is probably the most important qualification needed at this stage, and so I did my fair share of legal studies (in Swedish, a language I do not speak so well).</p><p>This was also the month when our imagiCharms were finally mass produced! But I have to give credit to Beatrice for all the learnings around bringing our imagiCharms to life, which she already summarized in a <a href="https://medium.com/imagilabs/what-happens-after-your-hardware-product-gets-funded-on-kickstarter-c28ade38d57e">separate post</a>.</p><p>By the beginning of <strong>April</strong> we learnt how to turn a physical event into digital — in fact we helped<a href="https://www.linkedin.com/posts/dorapalfi_being-a-startup-founder-means-lots-of-risk-activity-6651905877458599936-MJ3Y"> Womengineer’s annual Introduce a Girl to Engineering day go online</a>. Livestreaming on Twitch, running a coding contest on Discord — we picked up new tools along the way.</p><figure><img alt="Screenshot of Twitch livestream with Dora teaching for loops" src="https://cdn-images-1.medium.com/max/800/0*hfeYCv5GvfqdZWtV" /><figcaption>⚡️300+ girls watched our livestream on <a href="https://www.linkedin.com/company/twitch-tv/">Twitch</a> for IGE Day!</figcaption></figure><p>This event however, was also a big stress test to our app (which at this stage was due to go live in the App store in a month) and we learnt about an array of bugs and usability problems that needed fixing.</p><p>What I remember from the rest of April is trying to improve as a designer. Not as a self-improvement exercise but rather to drastically improve our app pre-launch. I again learnt that asking for help is a strength and thanks to a quick <a href="https://www.linkedin.com/posts/dorapalfi_ux-ui-appdesign-activity-6655407138535415808-etbJ">LinkedIn post</a> and a few direct messages I got an inflow of support! I read <a href="https://bradfrost.com/blog/post/atomic-web-design/">Atomic design</a>, I talked to Chief Design Officers, read Figma’s documentation to the last pixel… and attempted to create a design system to help the Dev team&#39;s (at the time that meant Paula) and the Design team’s (at the time it was only me) collaboration.</p><figure><img alt="Dora pitching in front of the Sharks" src="https://cdn-images-1.medium.com/max/1024/0*StQ7IosML4nhDdn3" /><figcaption>One of the scariest things I did this yearwas pitching in front of the Sharks 🦈</figcaption></figure><p>Being overly consumed by designing and improving our product, in <strong>May</strong> I learnt that one should have planned in advance how to take advantage of TV appearances (this is when Shark Tank went live) and good PR. I also learnt that just launching an app is not enough. Promotion is half of the story and so I needed to switch gears! I spent two weeks filming short videos with coding challenges (for our #imagi30daysofCode) for our app, but by <a href="https://www.linkedin.com/posts/dorapalfi_imagi30daysofcode-femalefounders-stemathome-activity-6671067271122706433-nVt_">day12</a> I was able to hand over the task, among others, to our incredible imagiGirls. Keeping in mind the lesson that effective founders keep firing themselves from jobs.</p><figure><img alt="Screenshot of Hedvig&#39;s Youtube video" src="https://cdn-images-1.medium.com/max/1024/1*_o_S0Hc5JGCc-Za2NptOHg.png" /><figcaption>Hedvig, one of our imagiGirls introducing the Day12 challenge</figcaption></figure><p><strong>June</strong> marked the first time in the history of our company that we had imagiCharms in stock, waiting to be purchased. Suddenly, my most important job became sales. All the theoretical work I had done, hypothesizing what our acquisition channels would be, became a real-world experiment. We spent some time calling our existing customers to better understand how they have heard about us and I started testing several marketing and sales tactics, at all stages of our funnel. Someone more knowledgeable about sales and marketing would probably be shocked by how someone could get two years into a company without understanding much about SEO, ASO, performance marketing and several other tools and tactics, but again it probably happened just in time.</p><p>In <strong>July</strong> I had the chance to chat with Shelby Brown from <a href="https://www.cnet.com/news/girls-can-learn-to-code-with-the-help-of-this-new-smart-keychain/?ftag=COS-05-10aaa0d&amp;ServiceType=linked_in_page&amp;PostType=link&amp;TheTime=2020-07-11T11%3A01%3A03&amp;Ftag=ftag%3DCOS-05-10aaa0d&amp;UniqueID=CFA52AC8-C365-11EA-82BA-C0A64744363C">CNET</a>, and she wrote a wonderful review about our app. Learning to tell our story in a compelling and simple way continued to be an important exercise. While I was busy with sales and marketing, our product team exploded in size, thanks to 8 full time summer interns (many of them from our Alma Mater, NYU Abu Dhabi).</p><p>To me personally this meant learning a whole new way of communicating goals and progress to the team. I started to implement weekly all-hands meetings, structuring how we looked at our KPIs, and presenting the numbers and their implications to the team — no matter how bad or good they were.</p><p>In <strong>August</strong> the imagiCharms showed up for the first time in a retail store. To our surprise the first store we visited the store, the product was displayed with the “wrong” side up. Wrong might be relative and we learnt that we needed to rethink and give specific instructions if we want our display units to tell the story of the Charm. Meanwhile we established our first US-based partnership with DIY girls, an organization teaching girls to code in California which was followed by agreements for imagiCharms to be used as a teaching tool in five more countries, among them Stemettes, a UK-based nonprofit we had been hoping to work with since the earliest days of imagiLabs!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*d3eMCx7iv_t3aglS5lw3YA.png" /></figure><p>I also had the incredible chance to partake in my first professional filming experience (being on the other side of the camera), for the <a href="https://www.youtube.com/watch?v=1VKnT8sXe60&amp;ab_channel=imagiLabs">imagiCommercial</a>, which we launched in <strong>September</strong>. While with most things we do in a startup we aim to always iterate and continuously improve, this was a very different exercise. I learnt that in certain cases one needs to plan out every single detail.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AX50dCNi3PrYEuCKpQ2Kzw.png" /><figcaption>A busy filming day with our actors</figcaption></figure><p>Although we had listed the imagiCharm on Amazon in the summer, it wasn’t until <strong>October</strong> — come Prime day, that we suddenly started to see an increase in interest and sales. And this was the beginning of a continuous struggle with managing inventory, shipping and learning about the countless tools and platforms within Amazon’s seller central.</p><p>By <strong>November</strong> I had extensive experience pitching via video and speaking on online panels (a very 2020 specific learning) and thanks to an invitation to speak along panelists from Minecraft and Lego I had the opportunity (healthy pressure) to quickly expand my knowledge about the intersection of gaming and education, a learning journey that I am still at the start of. In November I also le-learnt a lesson about showing up. It is so easy to get stuck “inside the building”, and keep our heads down, keep busy building. But making the effort to physically attend a middle school class, and seeing how teachers use the imagiCharms in their classrooms wasn’t just a rewarding experience but also extremely insightful.</p><p><strong>December</strong> has been a thrilling month with the holiday rush, and I am excited about all the new imagiCoders joining our community who have received their imagiCharms under their Christmas trees. This month has been about caring for customers and users. Our team has collectively handwritten over 200 Christmas cards, we have been personally responding on all platforms where customer queries emerge, be that email, twitter, Discord, our website’s chat, or of course within our own app! We are still just starting to learn about all the ways in which we can show up for our customers! I also continue to learn that taking the time to reflect is an incredible exercise to breed confidence and put things in perspective.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/828/1*BecVvkagK9RaHgj3US878g.jpeg" /><figcaption>Holiday greetings cards ready to be sent!</figcaption></figure><p>Adding to Melanie Parkin’s observation, my extra cent is that every time I, as founder and CEO, felt like I learnt something properly it probably meant I had been spending more time on it than I should have. I probably should have trusted someone more equipped (with skills, talent and/or time) to take on the task. Luckily, thanks to an incredible team, interns, mentors and friends helping imagiLabs out I have been able to always move onto the next thing that needs quick learning and fixing.</p><p><strong>What&#39;s next?</strong></p><p>In 2021 we will continue growing our community of imagiCoders, and improving the experiences we curate for gaining coding superpowers through play! Naturally, this will require a lot of learning from our side, which we will hopefully continue to do just-in-time (or at least not too late).</p><p><em>PS. This is a reflection/ account from my personal perspective and without serious rigour to include everything. In fact, most things I learnt in 2020 are not included here. Still, if you are an aspiring entrepreneur you might find value in seeing some of the everyday learnings of a startup founder or if you are a fellow entrepreneur you might recognise familiar patterns.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bed22d86ac93" width="1" height="1" alt=""><hr><p><a href="https://medium.com/imagilabs/a-startup-year-full-of-just-in-time-learning-bed22d86ac93">A startup year full of just-in-time learning</a> was originally published in <a href="https://medium.com/imagilabs">imagiLabs</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What happens after your hardware product gets funded on Kickstarter]]></title>
            <link>https://medium.com/imagilabs/what-happens-after-your-hardware-product-gets-funded-on-kickstarter-c28ade38d57e?source=rss----cc4dacbcbf16---4</link>
            <guid isPermaLink="false">https://medium.com/p/c28ade38d57e</guid>
            <category><![CDATA[kickstarter]]></category>
            <category><![CDATA[crowdfunding]]></category>
            <category><![CDATA[manufacturing]]></category>
            <category><![CDATA[covid19]]></category>
            <category><![CDATA[hardware]]></category>
            <dc:creator><![CDATA[Beatrice Ionascu]]></dc:creator>
            <pubDate>Fri, 23 Oct 2020 18:31:38 GMT</pubDate>
            <atom:updated>2020-10-23T18:34:02.732Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="the imagiCharm and its packaging surrounded by pantone color palettes" src="https://cdn-images-1.medium.com/max/747/1*YB0MfO_inkG4rY9w8WzKWw.png" /></figure><p>Our imagiCharm Kickstarter campaign was not an instant success. It didn’t get funded on the first day, or the second one, like some of the Kickstarter success stories we had been researching while preparing our campaign. It finally reached its funding goal with 15 hours to go after 30 days of continuous teamwork promoting <a href="https://www.kickstarter.com/projects/imagilabs/imagicharm-the-accessory-every-girl-will-love-to-program/description">the campaign </a>, refining how we explain our product and tell our story, understanding our customer, and exhausting our networks. But it happened. The campaign finally got funded on the last day and we were thrilled. Over 600 customers were now eagerly waiting for their imagiCharms. All we had left to do was bring this product to life and fulfill the hundreds of orders.</p><p>In this post, I detail how we were able to fulfill the hardware aspects of our promise to our Kickstarter backers. My hope is to show how much work went into delivering on our funded Kickstarter and show that this is doable-even for first-timers like us. I will give a high-level summary of the eleven months that followed the end of the campaign and share some of our learnings throughout this process.</p><p>Originally, we had set out to deliver our backers’ early bird rewards by Christmas and the rest in January, meaning within 6–7 months from the end of the campaign. This timeline incorporated knowledge and lead times from similar hardware startups. <em>Tooling? One to two months. Component lead times? Between zero and hundreds of days. Producing 2000 units? A few days. Shipping by air? A week. Shipping by boat? One to one and a half months. </em>Of course, this timeline was ambitious and it assumed that everything would go smoothly. If running the Kickstarter campaign can be compared to a sprint, the <a href="https://www.kickstarter.com/projects/imagilabs/imagicharm-the-accessory-every-girl-will-love-to-program/posts">almost year-long process that followed </a>was more like a marathon, with a “minor” blip along the way consisting of a worldwide pandemic.</p><h3>June: Campaign month</h3><p>Kickstarter has an all-or-nothing funding model, which means that you have to meet or exceed your funding goal by the deadline set when launching the campaign to receive any of the funds from your backers. Because of this, we carefully set a funding goal that, according to our estimates at the time, could cover most if not all of our upfront manufacturing costs. We ran a 30-day campaign, based both on Kickstarter and other people’s recommendations. On June 27 we hit the goal of the campaign and with the money raised, we were in a better position to negotiate with manufacturers.</p><figure><img alt="the imagiLabs team celebrating our successfully funded Kickstarter campaign" src="https://cdn-images-1.medium.com/max/1024/1*rbrk3sFel-lT3Q501P2Jig.jpeg" /><figcaption>The imagiLabs team celebrating the successful funding of our Kickstarter campaign.</figcaption></figure><h3>July: Request for quote (RFQ) period</h3><p>We had started asking for introductions to manufacturers through our networks in the months preceding the campaign. However, given the uncertainty regarding the success of our campaign and our lack of previous experience launching a hardware product, the conversations with the manufacturers hadn’t gone very far. In July, with both funding and preorders on our side, we picked up the conversations.</p><p>We started discussing quotes and timelines, and as we got more detailed design for manufacturing (DFM) feedback, we started incorporating it into the electrical and mechanical design of the imagiCharm. During this time we were also introduced to new manufacturers, including the one who would end up producing our imagiCharms. This last introduction came through the <a href="https://www.hardwareclub.co/">Hardware Club </a>, a community that has been invaluable for us in our journey as a hardware startup.</p><h3>August: Choosing the right contract manufacturer</h3><p>Our main criteria for choosing a contract manufacturer (CM) included having experience with similar products (both in terms of complexity and order size), being interested in helping us launch a quality product, and being willing to contribute their expertise towards improving the design of our product, challenging our decisions, and giving us feedback. Communication and transparency were also important. From our shortlist of potential CMs, one satisfied all of these criteria.</p><p>In August, we finalized the first version of the mechanical and electrical design of the imagiCharm. It included modifications from the original concept that would improve the manufacturability as well as the usability of the product: simplified inner plastic housing and separate silicone casing, channels to hold the string for the imagiCharm, and a more water-resistant charging port.</p><h3>September: First visit to the manufacturer</h3><p>It’s difficult to establish a business relationship over Skype. As both our first and second CM choices were based in Shenzhen, a trip to China to meet the manufacturers in-person was needed before signing. We were almost certain that we were going to work with Gadget Lab, our first choice. Given our tight timeline, we took the trip to confirm this decision and to review the first prototypes. Boris, our hardware engineer, joined me.</p><p>We spent a full day discussing changes that would need to be made to the electrical, mechanical, and packaging designs. In order to reduce complexity and cost, we had to drop some features we had invested a lot of effort and resources in, like water-resistance. Being in the same room with Gadget Lab allowed us to make several decisions on the spot. Over email, Skype, and WeChat these would have otherwise taken days, if not weeks.</p><figure><img alt="the imagiLabs team on a factory tour in Shenzhen, China" src="https://cdn-images-1.medium.com/max/1024/1*OkLZmv7PwuxsZdSj1vBMXA.jpeg" /><figcaption>Beatrice and Boris from the imagiLabs team on a factory tour in Shenzhen, China.</figcaption></figure><h3>October: Tooling stage</h3><p>In Shenzhen, we realized that given the pending design changes and our limited resources, we would not be able to stick to our original manufacturing timeline. We agreed on a new timeline according to which the imagiCharms would be ready by March, three months later than promised. Our backers were the first to know about the change. Throughout the campaign we always kept our backers up to date with our progress and also involved them in some parts of the decision-making process, like choosing the color of the imagiCharm. We recommend fellow crowdfunding startups to involve backers even more if possible.</p><p>Overall, in October, we were kept busy revising the electrical design and finalizing the mechanical design. Once the mechanical design was finalized, our CM’s chosen plastic factory built the injection moulding tool, a process that took six to seven weeks to complete.</p><figure><img alt="prototypes of various imagiCharm parts" src="https://cdn-images-1.medium.com/max/1024/1*g-JFx6E1PxwzreonbbwPvQ.jpeg" /><figcaption>Prototypes of various imagiCharm parts.</figcaption></figure><h3>November: Finalize electrical design</h3><p>In November, we finalized the electrical design, confirmed all the component suppliers, and the bill of material (BOM) costs. We had chosen Gadget Lab as our manufacturing partner because they are an original design manufacturer (ODM). This means that their team of experienced engineers and manufacturing experts supports the development of new products, starting with the design phase. They have their own network of factories and acted as a one-stop-shop, helping us with all stages of product development.</p><p>Although one of the advantages of working with a one-stop-shop is not having to worry about sourcing components, I recommend talking to suppliers directly when possible. By going directly to the source, we received better prices, enabling us to negotiate lower prices with our manufacturer.</p><p>After a few iterations and tests with our end users, we also settled on the final packaging design, including a first version of the packaging artwork. Testing the first prototype units was also a priority during this month.</p><h3>December: Firmware at last</h3><p>The team working on the imagiCharm consisted of a product designer, a mechanical engineer, a hardware engineer, all part-time, and a team lead, myself, overseeing the manufacturing and sourcing process, monitoring the timeline, quality, and regulatory considerations, while also writing firmware. With a small team like ours, it was not always possible to work in parallel on all the required tasks.</p><p>In December, with the mechanical and electrical designs in place, we were able to shift our focus almost exclusively to the firmware, meaning the code running on the microprocessor inside the imagiCharm. With a last push during the holidays, we finally finished a v1 firmware for factory testing purposes and developed a factory testing app. We also developed the functionality test procedure for the factory to test each assembled unit.</p><h3><strong>January</strong>: <strong>Pre-production stage</strong></h3><p>During the pre-production stage we had a smaller batch of units produced to verify that the production setup and the resulting units accorded with our specifications. We had these units made for marketing and regulatory purposes, however the validation they provided was paramount for finding any remaining or unforeseen issues before starting mass production.</p><p>I can’t emphasize enough the importance of the product team again being on the ground to review the results. This time only I went, which required very thorough preparation with our hardware and mechanical engineers to make sure I would not miss any details when reviewing the units. Being able to communicate right away with the rest of the team during the trip was also necessary. Thus, I recommend that multiple people participate in a similar trip, if possible, in order to split responsibilities and leverage each team member’s expertise.</p><p>Besides reviewing all the produced parts and confirming the material and color of the imagiCharms’ string, we also reviewed and adjusted the testing procedure that the factory would follow for both the pre-production and mass-production. By the end of the month, 60 pre-production units arrived in our office. Little did we know at the time that we had just pulled this through right before the onset of a pandemic.</p><figure><img alt="Testing procedure review in the factory meeting room" src="https://cdn-images-1.medium.com/max/1024/1*M1P2LBhAI0CHawu6lDkJAA.jpeg" /><figcaption>Testing procedure review in the factory meeting room.</figcaption></figure><h3>February: Lab test stage</h3><p>Another benefit of working with a one-stop-shop is that they have experience with the entire process, from design for manufacturing to factory selection to obtaining the required certifications. We were able to navigate the regulatory aspects through a combination of research on our end and their help.</p><p>In February, following the Lunar New Year holiday and the spike of COVID-19 spread in China, our manufacturing partner was able to slowly resume work. As testing laboratories reopened, we proceeded to start the laboratory testing needed for hardware certification. Meanwhile, we continued the firmware development work, thoroughly tested the pre-production units and created quality control guidelines to be used in mass-production.</p><h3>March: Mass production</h3><p>In March, after iterations of testing and bug-fixing, we finally signed off on the firmware. But over-the-air (OTA) firmware updates didn’t make the cut. If there is one main takeaway from this post, it is to always start with OTA, if applicable. Being able to distribute firmware updates to a hardware product post launch is instrumental in being able to fix bugs, maintain the product, and ideally ship improvements and new features. As you will see below, we ended up adding this feature right before starting to fulfill our backers’ rewards.</p><p>In this month we also finalized all the regulatory work and everything was finally in place for the imagiCharms to start production. While our manufacturing partner was busy with producing the parts, assembling and testing the units, our team started downscaling and focusing on the logistics and fulfillment.</p><p>The reality of a hardware startup is that the work comes in phases. With the product design and the mechanical and electrical engineering cycle now coming to an end, the day-to-day involvement of our product designer, mechanical engineer, and hardware engineer also ended temporarily. We are lucky to still have them on our team even though the months since March have been very quiet on this front.</p><h3>April: Logistics</h3><p>One significant flaw in our original timeline was not accounting for unforeseen events. The reality is that unforeseen events always happen. They can be as small as a wrong resistor value that needs to be changed last minute, or bigger, like an important component suddenly having longer lead times, or even bigger, like a world-wide pandemic wreaking havoc across most industries. With more experience, it’s easier to account for such happenings, although I’m not sure that even the most experienced would fare better during a pandemic-stricken world.</p><p>In April, our first batch of 2000 imagiCharms was produced and passed quality control. We continued researching logistics and fulfillment options and arranged for 960 units to be sent to Sweden by plane. The remaining 1040 were sent by sea freight.</p><figure><img alt="The first shipment of imagiCharms unloaded in front of the imagiLabs office" src="https://cdn-images-1.medium.com/max/328/0*rQqi_uB21QaytwQe" /><figcaption>The first shipment of imagiCharms unloaded in front of the imagiLabs office.</figcaption></figure><h3>May: Fulfillment</h3><p>We began our logistics and fulfillment research by looking into warehouses and third-party logistics solutions. Eventually we realized that we were getting ahead of ourselves. With the number of preorders that we had-just under 700-it would have ended up being very expensive to outsource our fulfillment. Doing so would have also removed an essential learning opportunity. A driving ethos throughout this process has been to do as much ourselves as we could to learn and build knowledge inside the company that can be used later on.</p><p>Finally, after several delays caused by COVID-19’s strain on the supply chain and transport systems worldwide, our 960 imagiCharms arrived in Stockholm on May 11. We started fulfilling our backers’ rewards on May 15. The four days in between were used to get a head-start on reprogramming the units and adding the missing OTA feature. Fun times…</p><figure><img alt="The imagiLabs team packing imagiCharms for our Kickstarter backers" src="https://cdn-images-1.medium.com/max/1024/1*eAVizAGFgzc1aDK8i93fzA.jpeg" /><figcaption>The imagiLabs team packing imagiCharms for our Kickstarter backers.</figcaption></figure><p>Given the high-level nature of this post, a lot of the work we did couldn’t make it into these paragraphs. Bringing the imagiCharms to life following our Kickstarter campaign was stressful and scary at times, but ultimately an educational and rewarding experience. We came out of it with not only our first 2000 imagiCharms but also infinite more knowledge and confidence to tackle future challenges, considering that at the beginning we had close to zero insight into what it means to create a hardware product, from R&amp;D to manufacturing and to delivery.</p><p>The most important lesson we learned was to always keep our backers up to date with our progress. We posted regular updates on our imagiCharms and also shared what we were up to each month beyond the realm of our hardware progress. We have our backers to thank for even being able to attempt this journey in the first place, so we always felt compelled to keep them in the loop with the latest developments, regardless of whether they were positive or negative. I believe our open communication and active engagement are part of why our backers were very supportive when our timeline had to be extended and are extremely supportive to this day, continuing to provide feedback and suggestions.</p><p>During this time, our team was also very busy creating the accompanying iOS and Android apps for the imagiCharm, coming up with learning content, securing investments outside of Kickstarter, running coding workshops, and experimenting with digital marketing channels. In sum, we were doing everything we could to make sure that imagiLabs, as a startup, was successful and fulfilling our mission of getting more girls interested in coding. But we would need a lot more than a blog post to cover all of that.</p><p><em>Thank you for the editing work done by</em><a href="https://medium.com/u/5880401408ea?source=post_page-----48f1a48e8ba9----------------------"><em> Melinda Szekeres</em></a><em>.</em></p><p><em>Originally published at </em><a href="https://imagilabs.com/blogs/news/kickstarter-funded"><em>https://imagilabs.com</em></a><em> on October 23, 2020.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c28ade38d57e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/imagilabs/what-happens-after-your-hardware-product-gets-funded-on-kickstarter-c28ade38d57e">What happens after your hardware product gets funded on Kickstarter</a> was originally published in <a href="https://medium.com/imagilabs">imagiLabs</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How I Became A Programmer, While Not Looking Like One]]></title>
            <link>https://medium.com/imagilabs/how-i-became-a-programmer-while-not-looking-like-one-33c330c69a2b?source=rss----cc4dacbcbf16---4</link>
            <guid isPermaLink="false">https://medium.com/p/33c330c69a2b</guid>
            <category><![CDATA[computer-science]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[imagilabs]]></category>
            <category><![CDATA[college]]></category>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[Brian Kim]]></dc:creator>
            <pubDate>Sun, 16 Aug 2020 08:06:00 GMT</pubDate>
            <atom:updated>2020-08-16T08:06:00.919Z</atom:updated>
            <content:encoded><![CDATA[<p>Growing up in an Asian household, I always assumed that I would pursue STEM. But during my last year of high school, I went to Italy where I took zero STEM classes and discovered joy in learning about different people and cultures. Soon, I found passion in mental health so I switched to Psychology. But during my time off in the Korean army, I found myself questioning my field yet again. So there I was, in my first semester back from the national service, taking my first programming class ever.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uBAgUVvQlSEJxIa-29Q4QQ.jpeg" /><figcaption>Me during the Orientation Week when I was certain I would never take a STEM class in college</figcaption></figure><p>I told my graduating classmates about my switch to Computer Science, and they all wanted to know why I made such a drastic change, since I didn’t “look like a programmer.” I didn’t blame them; I didn’t think so either. At that moment, all I knew was that I liked listening to and helping people, which is what initially drew me towards counseling. But I craved a more immediate, real-world applicable approach, so I decided to learn some programming. Plus, coding is used in any field of research, so I thought that it wouldn’t be a waste of time. I would give it a try for a semester and then decide if I should truly commit myself to yet another different major.</p><p>In this moment of discovery and confusion, I ended up going to Stockholm for a long weekend in early December with a friend. I was mostly going there for the ABBA museum, but she wanted some local suggestions, so she reached out to a few NYU Abu Dhabi alumni who invited us to their office for a quick get-together over tea — and that’s how I first stepped into the world of <a href="https://imagilabs.com/?utm_source=medium&amp;utm_medium=direct&amp;utm_campaign=medium-brian">imagiLabs</a>. As two of the co-founders, Bea and Dori, talked about their experiences since graduating from NYUAD and starting imagiLabs, I was awestruck by their entrepreneurship. They were tackling a problem very personal to them (gender inequality in STEM) with a technology-driven solution (teaching young girls how to code). And that moment, as I was listening to them talk about their passion, was when I realized why I should continue studying CS: to create real-world solutions to problems that I want to address.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sI2oZxzM5UJKvFKBDGxXrA.jpeg" /><figcaption>My friend and me escaping from Stockholm winter by jumping into a Greek summer scene of Mamma Mia</figcaption></figure><p>Less than a year later, I completed my two-months long internship at imagiLabs. As expected, I learned a lot about Swift and Xcode by working closely with full-time iOS developers and became a pro at GitHub, since everything was done remotely. But to my surprise, I also learned that a programmer does more than writing code; they think about the audience. As I participated in user story discussions during sprint planning and designed in-app learning content from scratch on Figma, I spent a lot of time brainstorming how to improve user experience. I found myself pondering questions about the needs and challenges of a typical English-speaking teenage girl, who is the target user of imagiLabs. This kind of thought process helped me grow as a programmer, who codes not for the sake of coding but for the sake of helping people.</p><p>I really believe that my internship at imagiLabs has taught me to put people first. So moving forward, I want to continue being part of projects that tackle social issues around me. In the next few months, I will be working for the Korean government as a Big Data Analysis intern to identify problems and propose policy solutions for my province. I hope that this experience, albeit in a different realm of programming, will further teach me how to use technology for bettering the lives of many.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NtU8LWF_XbzUQxO5fkqgqw.png" /><figcaption>My first ever hackathon team Nitaq that went all the way to winning the audience award!</figcaption></figure><p>I still feel uneasy about calling myself a programmer because I think the term by itself loses the nuance of the behind-the-scenes intentions. But as long as I am deliberate about the humans who will benefit from the tools I create, I think I can embrace this term.</p><p>So, yes, I am a programmer, while not looking like one.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=33c330c69a2b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/imagilabs/how-i-became-a-programmer-while-not-looking-like-one-33c330c69a2b">How I Became A Programmer, While Not Looking Like One</a> was originally published in <a href="https://medium.com/imagilabs">imagiLabs</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why gender equality in tech is a prerequisite for gender equality in society]]></title>
            <link>https://medium.com/imagilabs/why-gender-equality-in-tech-is-a-prerequisite-for-gender-equality-in-society-48f1a48e8ba9?source=rss----cc4dacbcbf16---4</link>
            <guid isPermaLink="false">https://medium.com/p/48f1a48e8ba9</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[women-in-tech]]></category>
            <category><![CDATA[gender-equality]]></category>
            <category><![CDATA[female-founders]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Dora Palfi]]></dc:creator>
            <pubDate>Tue, 04 Aug 2020 06:17:46 GMT</pubDate>
            <atom:updated>2020-08-04T06:17:46.579Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WqZsJiP-Nd0wzW4T04V_jA.png" /></figure><p><em>As a co-founder and CEO of a tech startup that builds products to teach coding to girls, I face constant scrutiny over our company’s mission and the need for our products in the market. Here I outline why we believe gender equality is so important to our future. In a subsequent post I will discuss how we have gone about formulating a solution to inequality in tech.</em></p><blockquote><strong>if: technology = future</strong></blockquote><blockquote><strong>and: women ≠ tech</strong></blockquote><blockquote><strong>then: women ≠ future</strong></blockquote><h3><strong>Tech is the future, yet women are not on track to participate in shaping that future</strong></h3><p>Tech is the most powerful industry in the world. It shapes the way we live our lives and enables us to create new businesses and solve problems at an unprecedented speed. The digital economy currently is <a href="https://www.brookings.edu/research/trends-in-the-information-technology-sector/#footnote-2">valued at $11.5 trillion globally</a>, comprising 15.5% of global GDP, and has grown two and a half times faster than total GDP over the past 15 years. The sector is also generating jobs at a disproportionate pace: the <a href="https://ec.europa.eu/eurostat/statistics-explained/index.php/ICT_specialists_in_employment">number of ICT specialists</a> in the EU grew by 39.1% from 2011 to 2018, six times greater than the increase in total employment.</p><p>Despite the clear importance of tech to our future, women are still severely underrepresented in the sector. In fact, a decreasing percentage of women are joining the industry today. In the EU, women make up <a href="https://ec.europa.eu/eurostat/statistics-explained/index.php/ICT_specialists_in_employment#ICT_specialists_by_sex">approximately 17% of the tech workforce</a>, a decrease from 10 years ago, when 22.5% of the ICT workforce was female. In the US, <a href="https://girlswhocode.com/about-us">37% of computer scientists</a> were women in 1995. Today, that figure stands at <a href="https://girlswhocode.com/about-us">24%</a>.</p><p>Closing tech’s gender gap matters for several reasons, including the <a href="https://hbr.org/2019/02/research-when-gender-diversity-makes-firms-more-productive">improved performance</a> that results from having more gender-diverse teams and the ability of women to fill the industry’s talent shortage. But what truly drives and concerns us at <a href="https://imagilabs.com/?utm_source=medium&amp;utm_medium=direct&amp;utm_campaign=medium-gender-equality">imagiLabs</a> goes beyond the health of the industry itself. We believe including women in tech is about economic fairness. The tech industry creates some of the best paying jobs. Women need to have the opportunity to pursue careers that will help them achieve financial security and independence.</p><p>Equally important, though, is the impact of who creates our technologies as we hurtle towards a future in which technology impacts every aspect of our lives. We must think about the implications for technology that, as former CIO of Verizon Judith Spitz <a href="https://www.youtube.com/watch?v=8H3kUd5MjGI&amp;feature=youtu.be">states</a>, is “destined to be the essence of who we are as a species,” and is being “developed largely under the leadership and guidance of a single gender.” <strong>If women do not have equal exposure and access to technology as a tool and as a career opportunity, we also miss out on an equal opportunity to shape our future.</strong></p><h3><strong>For technology to benefit everyone we need diversity among its creators</strong></h3><p>Tech has a gender bias problem. Societal biases and inequalities are being reproduced in the form of data inputs used to train AI algorithms and, therefore, being reflected back to us in the technologies we are creating. Biases also form when women’s experiences and perspectives are overlooked in the technologies and solutions that are being built. <a href="http://www.paulgraham.com/startupideas.html">Common startup advice</a> encourages founders to draw from their own experiences; who is going to identify the problems and create solutions for women and people who are not adequately represented in the tech industry?</p><p>Some of these biases might result in mild inconveniences and awkward laughs. In 2019, the Hungarian edition of <em>Forbes</em> published an <a href="https://forbes.hu/uzlet/mar-az-apple-is-felfigyelt-a-magyar-lanyra-aki-kutyuvel-batoritja-programozasra-a-tinilanyokat-imagilabs-imagicharm-palfi-dora/?fbclid=IwAR1nAEG1LM0GNFNBWLtEQ2Sdsobt_3Cc09CHSTF-QzN7LoOcuZcsv0oyYMw">article about imagiLabs</a>. Because we all have friends around the world who speak many different languages, the article often was subjected to Google Translate. After translating the article, many of my friends asked me, “Dora, why do they refer to you as ‘he’ in the article?”</p><p>The Hungarian language doesn’t have gender-specific pronouns, so in translating the article into languages that do, such as English, it was up to Google Translate to determine the appropriate pronoun. Since the article mentioned that I was a CEO, and more specifically a tech CEO, the Google Translate algorithm presumably made an “educated guess” that I would more likely be male than female.</p><p>Oftentimes, however, these biases negatively impact women’s lives by demonstrably reducing their wealth, opportunities, and prospects. For example, the algorithm developed to establish credit limits for the Apple Card had the effect of limiting women’s access to capital as exposed by <em>Ruby on Rails</em> creator David Hansson. In a <a href="https://twitter.com/dhh/status/1192540900393705474">Nov. 2019 tweet</a>, Hansson reported that despite his wife’s better credit score and their jointly managed finances, he still received an Apple Card credit limit that was 20 times greater than hers. This wasn’t an isolated incident; even Apple co-founder <a href="https://twitter.com/stevewoz/status/1193422616016519168?ref_src=twsrc%5Etfw%7Ctwcamp%5Etweetembed%7Ctwterm%5E1193422616016519168%7Ctwgr%5E&amp;ref_url=https%3A%2F%2Fwww.businessinsider.com%2Fapple-card-sexism-steve-wozniak-2019-11">Steve Wozniak responded</a> that he had had the same experience. In response to the Twitter thread, Apple indicated that it was Goldman Sachs’ fault. <a href="https://twitter.com/gsbanksupport/status/1193703266003177472?ref_src=twsrc%5Etfw%7Ctwcamp%5Etweetembed%7Ctwterm%5E1193703266003177472&amp;ref_url=https%3A%2F%2Fwww.businessinsider.com%2Fapple-card-faces-investigation-over-gender-discrimination-allegation-2019-11">Goldman Sachs, in turn, said</a> it was “the algorithm’s” fault.</p><p>The list of tech industry misses and errors go on: <a href="https://www.theverge.com/2016/1/11/10749932/vr-hardware-needs-to-fit-women-too">VR headsets</a> that don’t fit women’s heads; <a href="https://hbr.org/2019/05/voice-recognition-still-has-significant-race-and-gender-biases">voice recognition</a> that doesn’t recognize female voices; <a href="https://www.independent.co.uk/life-style/women/apple-iphone-xs-max-new-too-big-size-women-sexist-feminist-a8537171.html">phones</a> that don’t fit women’s hands or pockets (together with technologies that assume everyone carries their phones in their pockets).<strong> These errors would almost certainly be less likely to occur if we had more women among the creators of our products and technologies.</strong></p><p>Women can and will identify markets that would otherwise remain underserved and overlooked. While menstrual cycle tracking was <a href="https://www.ft.com/content/b8f5c1e2-1803-11ea-9ee4-11f260415385">initially missed by Apple</a> in its “comprehensive” health monitoring system, female entrepreneurs, like Clue-founder Ida Tin, stepped in to cater to this need. Tin is not the only one: women entrepreneurs are creating solutions to a wide array of overlooked problems, most of which are experienced by women.</p><p>The question, then, is: how do we attract more women into the tech sector?</p><p><strong>How focusing on girls between the ages of 11 and 16 can fix tech’s leaky pipeline</strong></p><p>The lack of women in the tech industry has been described as the result of a leaky pipeline: at every step of the way from high school to college to early career, women are dropping out. As a woman in tech I have observed and experienced this phenomenon first hand. But I have also been involved in and benefitted from initiatives for women in the industry, and I have set out to create a meaningful impact on the pipeline of women in tech. I started by digging into the research and data to provide guidance on where I could create the most significant change.</p><p>According to a <a href="https://blog.google/outreach-initiatives/education/google-and-gallups-computer-science-education-research-six-things-know/">study on primary school computer science education in the US</a> conducted by Google and Gallup, there is no difference in interest in computer science between boys and girls at age 12. However, a significant gap is created from the ages of 12 to 14, when 47% of boys report being very interested, but only 12% of girls express interest.</p><p>We see a similar phenomenon in Sweden, where up until age 11 boys and girls show similar interest in technology, according to data collected by the Swedish Schools Inspectorate. However, <a href="https://media.sv.igeday.com/2020/01/How-to-inspire-girls-to-pursue-engineering.pdf">as discussed by Womengineer</a>, a nonprofit organization promoting engineering to girls, the percentage of girls who claim to be interested in technology “drops from 86% at age 11 to only 37% at age 15.”</p><p>Given that girls’ interest in technology drops dramatically between the ages of 11 and 16, we at <a href="https://imagilabs.com/?utm_source=medium&amp;utm_medium=direct&amp;utm_campaign=medium-gender-equality">imagiLabs</a> have decided to focus on this critical age range. Our goal is to engage girls when they are most likely to be interested in tech and use the power of community and shared interests to maintain their engagement as they get older. Our thesis is that by providing tools and a community at the right age, and doing so through a scalable solution, we can contribute to equipping and empowering the next generation of female engineers, developers, and tech founders.</p><p><em>To be continued… This is part 1. In the next part, I will talk about how we have gone about formulating a solution to gender inequality in tech. Stay tuned! 🙌</em></p><p><em>Thank you for the editing work done by </em><a href="https://medium.com/u/5880401408ea?source=post_page-----48f1a48e8ba9----------------------"><em>Melinda Szekeres</em></a><em>. While the examples collected in this article were mostly contributed by the imagiLabs team, Caroline Criado-Perez’s “Invisible Women” has made a huge impact on my thinking about the gender data gap. For anyone interested, we highly recommend reading!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=48f1a48e8ba9" width="1" height="1" alt=""><hr><p><a href="https://medium.com/imagilabs/why-gender-equality-in-tech-is-a-prerequisite-for-gender-equality-in-society-48f1a48e8ba9">Why gender equality in tech is a prerequisite for gender equality in society</a> was originally published in <a href="https://medium.com/imagilabs">imagiLabs</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What I learned working remotely as a Mechanical Engineer for a startup]]></title>
            <link>https://medium.com/imagilabs/what-i-learned-working-remotely-as-a-mechanical-engineer-for-a-startup-f03157b08ce9?source=rss----cc4dacbcbf16---4</link>
            <guid isPermaLink="false">https://medium.com/p/f03157b08ce9</guid>
            <dc:creator><![CDATA[Veronica Lee]]></dc:creator>
            <pubDate>Tue, 21 Jan 2020 09:38:41 GMT</pubDate>
            <atom:updated>2020-01-21T13:49:15.240Z</atom:updated>
            <content:encoded><![CDATA[<p>Remote work is said to be a new workplace revolution: flexible schedule, zero commute time, autonomy in work-life. When faced with the decision of accepting a remote work offer from imagiLabs, I didn’t hesitate much. I knew I couldn’t move to Sweden, but I was sure I wanted to dedicate my time to building tools to empower girls in technology.</p><p>I was very aware of the many challenges I, and the rest of the team had to face. Working across different time zones (8 hours difference!) would require a lot of planning and time management. Morning standups would actually happen around 5 PM for me. Some meetings would run until 11 PM. Loneliness and missed opportunities to connect with people are also inevitable. No face-to-face interactions, no team dinners, no parties. But being an introvert by nature, I didn’t mind all of this. However, something I wasn’t at all prepared for was the challenge of making hardware remotely. I didn’t realise that I was about to become a full-time remote Mechanical Engineer.</p><p>After more than a year of remote work and the successful production of our first physical product, I would like to share some troubles we faced as well as ways in which we were able to overcome them. Long story short, making hardware remotely is hard, but possible at the highest quality level!</p><p><strong>Lesson #1: Communicating about hardware is VERY difficult.</strong></p><p>Hardware is by definition a physical product, it’s not a written document or a block of code on the screen. It’s offline. It needs to be touched, measured and evaluated physically. While Google Hangouts and screen sharing have made verbal interactions much easier, it is still impossible to communicate things like the surface texture or feel and strength of the material (still waiting for VR technology to solve this problem).</p><p>Having to rely on verbal communication, language becomes the limiting factor since there are only a few words to describe the vast range of physical properties. For example, we can have a smooth surface, a rough surface, a very rough surface, an extremely rough surface…?</p><p>Talking about 3D objects over calls is also tricky. I remember several instances when I would go on explaining a problem on “the front side of the product” only to realise that I never clarified which side I am referring to as the “front”. Being physically together also allows you to point at something and say “here, it’s wrong”, while we might otherwise spend over 10 minutes taking screenshots and drawing arrows and circles around the part we want to talk about.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Btez-EYDOdQ5UKcGYTeA8Q.png" /><figcaption>Actual screenshot of our workflow</figcaption></figure><p>Here are some essential tools that made our communication as painless as possible:</p><ul><li><strong>a 3D Printer</strong> is an absolute must for any team working with hardware products. It is impossible to agree on things like the size and shape of the product without holding the exact same object in your hand. Thanks to SolidWorks and Formlabs we have been able to replicate the same model in various environments and run identical tests regardless of<strong> </strong>location.<strong> I highly recommend investing in a maker-space membership or even buying a desktop 3D printer </strong>(you can find decent ones for as low as $300). The prototyping stage is vital to any product development cycle and it should not be tied to a specific office environment. Especially in small teams, it is very important for every member to be able to set up the prototyping process easily and replicate the product.</li><li><a href="https://grabcad.com/workbench"><strong>GrabCAD workbench</strong></a> was another life saviour. This software allows users to view and manipulate 3D files without having to install any software. While screenshots are great, it is vital to be able to study the model: rotate, scale, make cross-sections or change the transparency of the material to view inner contents. GrabCAD workbench allowed all of our team members (regardless of CAD skill level) to easily examine the product whenever needed.</li><li><strong>a phone with a good camera. </strong>Communicating through visuals is much more effective than through words. We took photos of everything: 3D prints, product samples, packages, manuals, screws, strings etc. I think my Google Photos will soon add a new category “imagiCharms” to the Things folder. Physical products never turn out exactly like computer renderings, thus it is essential to capture every detail and be able to communicate it with remote team members. A good camera became especially important when examining pre-production units received from the factory. We had to spot and communicate very minute visual defects, such as distortions, discolouration, scratches, misalignment or any unwanted marks. Sometimes the imperfection was easily spotted by the naked eye, but required almost a professional lighting setup in order to be caught on camera.</li></ul><p>Lesson #2 derives directly from the communication problem, and it is <strong>the importance of thorough documentation and a file naming system.</strong></p><p>Something as small as mislabeling one file or part could lead to huge confusion and a lot of wasted time. Imagine missing one component in your BOM (bill of materials), and thus receiving a very misleading price quotation from the factory? Even though one piece might cost 0.01$, when it comes to thousands of production units, there is no room for carelessness.</p><p>The file name is also crucial, it needs to be unique and descriptive. For example, our naming system includes a product name, material, part, version and date: imagiCharm_Plastic_Bottom_v10[12–14–2019], not Plastic_FinalFINAL (I know we all are guilty of this).</p><p>When it comes to documentation, we kept a record of every meeting, saved every screenshot and render. Not only does it make communication easier, but also saves a huge amount of time in case you later need to access an older file.</p><p>At imagiLabs we also worked hard to keep all documents very organised and accessible for each team member. If I ever needed to find out the electrical specification, I knew where to look instead of waiting hours for a remote team member to wake up in a different time zone and answer my Slack message.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*LpS0Nwnojl5hEFbK" /><figcaption><em>Enjoying the benefits of remote work: awesome desk with monitor all for myself</em></figcaption></figure><p><strong>How did working remotely help me improve?</strong></p><p>Lesson #3: <strong>Remote work greatly prepares you for working with overseas manufacturers.</strong></p><p>Working with Chinese factories is basically remote work unless you are based in China. At this stage, communication becomes especially difficult due to the language barriers and various styles of the workflow. However, by the time I had to explain our design and specifications to the factory in Shenzhen, I felt fully prepared for every step of the process. Whether it is sending over CAD files, explaining features through a Product Requirements Document, communicating CMF (colour, finish, material) or even explaining the unboxing experience through videos — we have done it all within our team.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/726/1*6fQRpxh3_3RLCQimsFnK0Q.jpeg" /><figcaption>Team meeting in progress</figcaption></figure><p>After a year of remote work with imagiLabs, I have just joined a new startup in Tokyo. I come to the office every day, commute 1 hour on the train, eat lunch with co-workers and am finally in the same time zone as the rest of the team. I am very excited about this change in my work style, specifically about the beauty of working together with other passionate engineers face-to-face.</p><p>If you ask me now whether I would recommend choosing remote work for Mechanical Engineers, my short answer would be <strong>no</strong>. However, I believe that remote work could be a great solution for many engineers who want to work from home or for an overseas company. With enough organisation, efforts to invest in the right tools and clear communication it is possible to produce great hardware on time without sacrificing quality. Perhaps career recruitment should be less tied to a specific location?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f03157b08ce9" width="1" height="1" alt=""><hr><p><a href="https://medium.com/imagilabs/what-i-learned-working-remotely-as-a-mechanical-engineer-for-a-startup-f03157b08ce9">What I learned working remotely as a Mechanical Engineer for a startup</a> was originally published in <a href="https://medium.com/imagilabs">imagiLabs</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A startup year in review — the founding story continued]]></title>
            <link>https://medium.com/imagilabs/a-startup-year-in-review-the-founding-story-continued-82e134d6c927?source=rss----cc4dacbcbf16---4</link>
            <guid isPermaLink="false">https://medium.com/p/82e134d6c927</guid>
            <category><![CDATA[female-founders]]></category>
            <category><![CDATA[year-in-review]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[founder-stories]]></category>
            <category><![CDATA[women-in-tech]]></category>
            <dc:creator><![CDATA[Dora Palfi]]></dc:creator>
            <pubDate>Tue, 31 Dec 2019 11:39:45 GMT</pubDate>
            <atom:updated>2019-12-31T11:39:45.360Z</atom:updated>
            <content:encoded><![CDATA[<h3>A startup year in review — the founding story continued</h3><blockquote><strong>We overestimate how much we can do in a single day yet we underestimate what we can achieve in a whole year</strong>.</blockquote><p>This really stuck with me from one of our team retro meetings. This point was raised by Boris, our hardware engineer and the reality of it really just hit me when I started writing this reflection. It’s been almost a year since<a href="https://medium.com/imagilabs/just-two-girls-making-the-world-a-better-place-a-startup-founding-story-54d745a786a6"> I wrote about the founding story and the first few months of imagiLabs</a> — and here is a short-ish and very honest account of the year that followed. 12 months taking us from pre-product and pre-funding to first founding and … closer to a launched product.</p><p>During 2019, every single day, <strong>I have constantly felt like I am behind</strong>. Not just a little behind on a few to-do items but buried by the amount of responsibilities I did not attend to (like unanswered emails, I am sorry, I am doing my best!). One of my biggest learnings this year has been how finite and limited time is and that <strong>every time I commit to doing a certain task I say no to a thousand others I could have accomplished.</strong></p><h4>With that let’s look through what we at<a href="https://imagilabs.com/"> imagiLabs</a> have said yes to in 2019.</h4><p>During the cold and dark winter mornings early <strong>January</strong> we were in the midst of <strong>redefining what imagiLabs’ first product should be</strong>. A fun accessory that can be customised through coding… we ran through our product designer (my high school classmate), Mate’s sketches again and again until we landed on the keychain accessory concept, and what eventually became the imagiCharm.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*l5MYtxS4C6jhIUsH" /></figure><p>We started <strong>February</strong> out by joining<a href="https://sting.co/en/"> Sting</a>, <strong>a start-up incubator</strong> in Stockholm. I like to think that Beatrice and I have been structured since the start but suddenly, there was so much organisation to everything we did. We learnt about all the things we were supposed to be doing, new ways of thinking about milestones, financing, marketing (pretty much all things non-product) that we hadn’t tried that we hadn’t yet, but most importantly we got to sit around a bunch of other crazy people like ourselves — entrepreneurs working on their dreams.</p><p><strong>In March we received our first larger grant</strong> which could be spent on salaries for our team. I remember staring at the email and being excited but not allowing myself to burst out in happiness just yet, knowing that I can’t fully trust my Swedish language skills. Quickly I asked a native Swede to confirm and indeed, after 12 months of working on imagiLabs and our dream without being paid and getting close to our financial limits, we were given support to continue focusing all our energies right here!</p><p>The same month, Ericsson officially became our customer. <strong>Our team went to Paris as part of our partnership with Ericsson</strong> and showcased our app and imagiCharm prototype at the UNESCO Mobile Learning Week.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*INafqjQxxvq7oVIzoCAL0Q.jpeg" /><figcaption>Beatrice was showcasing our early prototypes — soldered by her, 3D printed by me</figcaption></figure><p>Meanwhile, I was back in Stockholm at a networking event for the speakers of the upcoming Women in Tech conference when I received an email from Apple Developer Relations with great news and an interview invitation with a very short notice of 2 hours. Never mind that it was 8 pm in Stockholm already and I might have had a glass of wine. But the call went well, which leads us to April.</p><p>We spent the first two weeks of <strong>April</strong> in Cupertino — as part of the second cohort of <strong>Apple Entrepreneur Camp</strong>. On my 12 hour flight to San Fransisco I had all the time and space I needed to play around with our new brand created by a group of talented and big-hearted students from Hyper Island. For two weeks I was a full time designer again and we spent long hours white-boarding and redefining our app.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OmsGOSEup93yn0qzQxAxRw.png" /><figcaption>Old brand and design vs new. You don’t just spend 2 weeks at Apple without converting to dark theme.</figcaption></figure><p>We came back from sunny California filled with confidence — Tim Cook tweeted about us and<a href="https://medium.com/@pauladozsa"> Paula</a> had agreed to soon quit her full time position as a software engineer in Hong Kong, and join us as co-founder and lead developer full-time in Stockholm! But back in Stockholm I was up against a new battle I had never done before: <strong>closing our first investment round</strong>. By early <strong>May</strong> we got together a great group of investors who are just as excited about equipping and empowering young women with skills and confidence to learn to code as we are. I am eternally grateful for all the tips, pep talks and support other founders, friends and our business coaches gave during this time. Reading <a href="https://www.amazon.com/Venture-Deals-Smarter-Lawyer-Capitalist/dp/1119594820/ref=dp_ob_title_bk">Venture Deals</a> was also immensely helpful.</p><p>By the time I managed to finish the investment paperwork we were in full<a href="https://www.kickstarter.com/projects/imagilabs/1243669257/preview?ref=pbuild_dashboard#project-preview"> <strong>Kickstarter</strong></a><strong> </strong>preparation: shooting our video, working with our ambassadors, building our marketing materials. Finally, on the 28th of May we launched our campaign. The entire month of <strong>June was filled with anxiety, sleepless nights, excitement</strong>, questioning and not giving up. We didn’t have an easy ride. After the initial momentum of having our early fans pre-order their imagiCharms, things slowed down. It was painfully slow. But through close to something like a miracle in the end we made it — with an inflow of support in the last 24 hours, close to 600 imagiCharms were pre-ordered and we hit our goal. (Kickstarter works with an all or nothing model — if the goal is not reached the creators do not receive any of the funds/ pre-orders).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nytIuOqZK8e92u8kFIKaYQ.jpeg" /><figcaption>Our Kickstarter launch party</figcaption></figure><p>I thought <strong>July</strong> was going to be a month of recovery and soul searching, but actually there was no time to rest -yet, even if the months before had been tough on us. But here we were <strong>one year after the official registration</strong> of our company — so much has happened, so we did take at least a moment to celebrate that!</p><p>I was at Almedalen, the so called politicians’ week in Sweden as one of the finalists of a startup competition, <a href="http://theserendipitychallenge.se/">Techarenan</a>. At Almedalen we met with Emelie from <a href="http://womengineer.org/">Womengineer</a> — another organisation working to fix the gender imbalance in tech &amp; engineering. I know about a lot of organisations with a similar mission and finally met someone who just like me said it out straight: we have the same goal, we should collaborate. Finding meaningful partnerships is tough and important and I am really excited about where this will take us!</p><p>I was in London for a short day and a half. We have been part of a community of Hardware startups, called the<a href="https://www.hardwareclub.co/"> <strong>Hardware club</strong></a> and I showed up in-person hoping to become a more engaged member of the community. We found our manufacturing partner through some of the other companies in the club so it was a worthwhile trip.</p><p>The month of <strong>August</strong> was our peak <strong>intern season</strong> with 4 interns working side by side with our small team. Paula’s big move to Stockholm was another highlight. We spent our days working hard (mostly on our product) and late afternoons taking in the sun and warmth of the Swedish summer. I read the book<a href="https://www.amazon.com/Measure-What-Matters-Google-Foundation/dp/0525536221"> <strong>Measure what matters</strong></a><strong> </strong>as I was struggling to understand how one actually structures setting goals and tracking progress for a company. We also programmed Instagram filters with our ambassadors (the imagiGirls).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/949/1*U5gF405BBDEkAX26ilPPkQ.png" /><figcaption>Intern season!</figcaption></figure><p>In <strong>September</strong> we traveled. While Beatrice was in <strong>China</strong> <strong>meeting potential manufacturers</strong> I was <strong>in the US</strong> as part of a <strong>program for young European entrepreneurs </strong>called<a href="http://www.gmfus.org/ytili-fellowship"> YTILI</a>. I always struggle to know how much time I should be spending learning versus executing. But I was in a moment of so many questions. We were without our head of marketing, and I was managing the task. During my 10 days in Seattle and DC I met some incredible young people running inspiring companies across Europe and I had the time to just talk and talk and learn from them. We also went to the National final of Venture Cup, a startup competition in Sweden — where we did not win. We took home two awards (and the $ it comes with) in the regional final back in May, but you cannot have it all right? On the other hand, Forbes Hungary wrote an <a href="https://forbes.hu/uzlet/mar-az-apple-is-felfigyelt-a-magyar-lanyra-aki-kutyuvel-batoritja-programozasra-a-tinilanyokat-imagilabs-imagicharm-palfi-dora/?fbclid=IwAR3gDCn5rfswu4Wdr_I_4QzzjP3_K9ioDFk2KKM6sbcIaHTXwOxRNLlrP5w">article</a> about us and since then my family hasn’t asked when will I go back to finish my masters degree.</p><p>In <strong>October</strong> I went to Berlin for the first part of the <strong>Google for Startups</strong> Female Founder program. I loved the pragmatic support, a company as large as Google but still remembering the days it was a startup has provided specific advice on how to make app development and go to market roadmaps. We faced the reality that we won’t be able to ship the first imagiCharms before March, and as soon as it was confirmed, we told our Kickstarter backers.</p><p><strong>November</strong> we spent the most <strong>time with our users</strong> again and that is always a simultaneously excruciating and exhilarating experience. On <strong>one Saturday morning alone, we taught coding to 270 girls</strong> using (partially) handmade imagiCharms (thank you Beatrice &amp; Boris!) and our app. We went through a rollercoaster ride of feelings — our product is awful, it’s not ready yet. It does not work. On the other hand hey it works and there are people who are waiting for it and who are using it. What is more, week after week we got to see the excitement of girls as they were writing their first lines of code and saw the imagiCharms light up!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iyZ9qqAup_fFaYxFzQIEgQ.jpeg" /><figcaption>And in November we even had the chance to teach moms &amp; daughters to code!</figcaption></figure><p>I also spent a whole lot of time thinking about our reason for existence, our narrative. It was sparked by the 25 minute talk I had to give at Slush, a huge (and dark) tech conference in Helsinki.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*-PHjP9UKoDt5INqL" /><figcaption>If you want to force yourself to really think about the story behind your startup agreeing to give a talk is a great strategy.</figcaption></figure><p>We haven’t quite stopped working even over the holidays (startup life — I guess, Beatrice is actually spending the first day of the new year traveling to Shenzhen) and even when we do my brain keeps ticking about imagiLabs. But December is a great time to take a few hours to focus on reflection, check in on progress and appreciate all that has been achieved this year, a much needed exercise that I definitely recommend!</p><h4>What’s next?</h4><p>A whole lot of work to get the imagiCharms and our app out to the market in 2020 and along the way making the tough decisions — <strong>what are the things we should say yes to?</strong></p><p><em>PS. This is a reflection/ account from my personal perspective and without serious rigour to include everything. In fact, most things we did in 2019 are not included here. Still, if you are an aspiring entrepreneur you might find value in seeing some of the work a startup founder does or if you are a fellow entrepreneur you might recognise familiar patterns.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=82e134d6c927" width="1" height="1" alt=""><hr><p><a href="https://medium.com/imagilabs/a-startup-year-in-review-the-founding-story-continued-82e134d6c927">A startup year in review — the founding story continued</a> was originally published in <a href="https://medium.com/imagilabs">imagiLabs</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A woman’s place is in the (construction site of a solar-powered) house]]></title>
            <link>https://medium.com/imagilabs/a-womans-place-is-in-the-construction-site-of-a-solar-powered-house-1f93e299844c?source=rss----cc4dacbcbf16---4</link>
            <guid isPermaLink="false">https://medium.com/p/1f93e299844c</guid>
            <category><![CDATA[women-engineers]]></category>
            <category><![CDATA[women-in-tech]]></category>
            <category><![CDATA[nyu-abu-dhabi]]></category>
            <category><![CDATA[mechanical-engineering]]></category>
            <category><![CDATA[building]]></category>
            <dc:creator><![CDATA[Veronica Lee]]></dc:creator>
            <pubDate>Tue, 20 Aug 2019 11:18:32 GMT</pubDate>
            <atom:updated>2019-08-20T11:18:32.728Z</atom:updated>
            <content:encoded><![CDATA[<p>Before starting my undergraduate studies I was told that college is a place which will expand my boundaries and push me outside of my comfort zone. And that was definitely true in my case, as my university experience included living abroad for the first time, taking all of my classes in English, which is my second language, and majoring in Mechanical Engineering.</p><p>I have indeed encountered many uncomfortable situations both in and out of the classroom. But these are the experiences that have developed my passion for building things that will forever guide my career path. I love technology and the feeling of developing something new is one of my favorite in the world. Whether it is on the screen, or in real life — being the creator is simply awesome! It could be scary to put yourself in various challenging environments, but I personally believe that the skills and satisfaction you get are worth it!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*c-6emSUqSbDtMtGDqqPIhw.jpeg" /></figure><p>For example, in my senior year I was on the team building a full-size solar-powered house in the UAE as a part of the Solar Decathlon Middle East Competition. After countless sleepless nights in the Engineering Design studio on my campus, we spent the whole month on a hot construction site working 15-hour shifts.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YPrTFie71yR06uPZgr3NYA.jpeg" /><figcaption>Team NYUAD during our house presentation</figcaption></figure><p>My daily tasks ranged from cutting massive insulation panels to installing a solar water heater on the roof and building a wooden deck. That month turned me into a full-time builder: a hard hat was my main accessory and my outfit options varied between oversized construction pants and extremely oversized construction pants (they need to make these in smaller sizes by the way). It was definitely one of the most challenging times during my college years, and by the end of it I was exhausted mentally, physically and emotionally. But the feeling of pride knowing that I can now operate a forklift and every type of electric saw was so rewarding, that I don’t regret a single second that I spent burning under the hot UAE sun. “Hey mom, I built a house” — was one of the coolest things I got to say during my undergraduate period.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wZYlZtflosxwxQ0TZZVpqw.jpeg" /><figcaption>Lunch inside the forklift because it has a very comfortable seat</figcaption></figure><p>Needless to say, it wasn’t just the heat and physical fatigue that made the process challenging. Many things failed during construction, the team dynamics struggled during tough times, the motivation wasn’t always there and sometimes I just really missed my bed. Just like with any big project, you are on a roller coaster and can never predict the type of tasks you’ll have to take on. The prospect of a group of inexperienced undergrads building a solar house sounded very intimidating at first, and it didn’t get any easier until we had our first meal in that very house. I learned many lessons during this project, and one of them is: <strong>you HAVE TO get uncomfortable and learn on the spot to pursue an idea you believe in. </strong>Hands-on skills, experience and even self-confidence are all acquired, but you will never learn unless you make a decision to throw yourself into the unknown. Every day of mastering power tools increased the confidence in my skills and reinforced my passion for creating useful things that solve real problems.</p><p>And these problems can range from building solar-powered houses to solving the lack of female representation in tech. That is why I joined imagiLabs, which is on a mission to empower girls to pursue careers in tech. Striving to be a maker myself, I couldn’t miss the opportunity to include more girls in this creative process of building new products that shape the future. And because I fully understand the challenges of diving into a STEM field, I am very inspired to provide girls with the necessary tools to spark their passion.</p><p>I am excited to build the imagiCharm not only because it teaches programming, but primarily because I believe it will help <strong>increase girls’ confidence and inspire them to step forward. </strong>B<strong>​</strong>ecause at some point girls may realise that the same for-loop logic they mastered while creating a pink heart on the imagiCharm is a first step to a complicated AI algorithm. ​<strong>And it’s not scary anymore.</strong></p><p>I believe we all strive for creativity in our work and coding is a tool which should never become a barrier for self-expression and idea realization. I am excited to see the next generation of makers create the technologies of the future!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1f93e299844c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/imagilabs/a-womans-place-is-in-the-construction-site-of-a-solar-powered-house-1f93e299844c">A woman’s place is in the (construction site of a solar-powered) house</a> was originally published in <a href="https://medium.com/imagilabs">imagiLabs</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What it means to learn coding as a social scientist]]></title>
            <link>https://medium.com/imagilabs/what-it-means-to-learn-coding-as-a-social-scientist-3617cf813d2?source=rss----cc4dacbcbf16---4</link>
            <guid isPermaLink="false">https://medium.com/p/3617cf813d2</guid>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[data-analysis]]></category>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[college]]></category>
            <dc:creator><![CDATA[Soohyun Hwangbo]]></dc:creator>
            <pubDate>Fri, 02 Aug 2019 08:15:18 GMT</pubDate>
            <atom:updated>2019-08-02T08:15:18.828Z</atom:updated>
            <content:encoded><![CDATA[<p>I dived into my first programming class — Introduction to Computer Science — in my first semester of college and, as much as I was intrigued by the entirely different system of logic, I was also stressed out for not being able to excel in it as I wanted. My classmates seemed to move forward when I remained stuck with bugs in my program, unable to figure out the problem despite asking around and spending nights at the lab. While it was a natural part of the learning curve that most people would have faced in the initial stages of programming, I was frustrated with myself for not being able to understand the material fully.</p><p>By the end of the semester, I couldn’t shake off the feeling that I was lagging behind. At the back of my head I was still questioning myself — why do I want to learn it? What do I hope to do with coding? I couldn’t see myself working as a programmer (at that time I also had a very limited understanding of what studying computer science was like). But I still had a longing to find what I could do with coding and continued poking around for different ways to engage myself.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*umsimnjmcQc7vdfPAntQtA.jpeg" /><figcaption>Back in the days of a confused freshman</figcaption></figure><p>What immensely changed my perspective on learning coding was taking a Data Analysis course in the Fall semester of my sophomore year. There, I learned R programming and how to analyze data in social science contexts. My political science professor was an avid user and advocate for R (with his frequent appearances to class wearing an R conference T-shirt). Prior to the class I was unaware of the sheer amount of statistics and quantitative methods involved in social science research — I thought coding was only used for making applications and programming as a ‘software engineer’. Little did I know that it could be used in <strong>so many different fields, regardless of the discipline.</strong></p><p>Throughout the class I learned so much, picking up packages like Tidyverse and visualizing data with ggplot. I also found that having some background in Python immensely helped me; R syntax is similar to that of Python, so the code writing logic came more at ease. One of the most memorable projects in that class was analyzing data for a fictional Bangladeshi NGO, where we had to go through 50,000 survey data points containing information on arsenic poisoning of wells to examine the relationship between well safety, healthcare costs, poverty, and education. We were asked to create policy proposals based on meaningful analysis from a messy data set.</p><p>During this project I realized that the aim of programming is not only to write ‘correct code’ — above all it requires you to <strong>first lay out frameworks on how to approach the problem</strong> and then narrow down what results you want to get through coding. In this case I had to consider how to make findings from the data accessible to a general audience as well.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*bP9pcGMsJdGwbg6x" /><figcaption>Part of my project in R Markdown</figcaption></figure><p>I loved breaking down problems in such perspective, and actually found myself enjoying coding within this process. Once I saw the reason ‘why’ I needed coding, I gradually started to appreciate the process of learning — including overcoming my fear of bugs and coder’s block.</p><p>Being able to code empowers you in a way quite similar to learning a new language, and opens so many new doors for you. Even in my field of interest — sociology — researchers are extensively using programming not only to facilitate data collection, but also to run complex statistical models (such as Bayesian inference). There are Python libraries for text analysis and R packages like <a href="https://github.com/pablobarbera/Rfacebook">Rfacebook</a> that collect information from public posts using specific keywords to examine how social media affects political participation. These can grant much liberty to how people conduct their research and expand the research scope.</p><p>Two years since that first programming course, I am now an intern for a company that teaches programming to teenage girls. My time at <a href="http://imagilabs.se/">imagiLabs</a> had been packed with exciting, fast-paced work — I have been mainly working on identifying and delivering new business insights, as well as learning about the workflow that goes into launching an application. And the internship also propelled my motivation to equip myself with more tools. In the next few years I hope to take more statistics and coding classes, and take part in projects that would involve analyzing data for actionable policy proposals to improve the community around me.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OwgXP4TWGLvZB4L5oU7nHw.jpeg" /><figcaption>Together with the imagiLabs team for the summer!</figcaption></figure><p>I am not pursuing a Computer Science major as I had considered in my first semester. After days of indecision, late-night conversations with people for advice, and multiple changes to my academic plan, I realized that my interests lie in the study of the society. Yet there are still so many reasons to learn programming because it<strong> empowers you in an entirely new way to gain deeper insights of the problems in society</strong>. You don’t need to be a Computer Science major to have fun coding, or use coding in your work. Rather than viewing it as an alien language that requires ingenuity to decipher, it should be approached as another form of problem-solving. I still have a long way to go, and much left to work for, but I am ready to brace myself for more learning opportunities and coding to come.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3617cf813d2" width="1" height="1" alt=""><hr><p><a href="https://medium.com/imagilabs/what-it-means-to-learn-coding-as-a-social-scientist-3617cf813d2">What it means to learn coding as a social scientist</a> was originally published in <a href="https://medium.com/imagilabs">imagiLabs</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>