{"id":1698,"date":"2019-05-15T03:37:57","date_gmt":"2019-05-15T03:37:57","guid":{"rendered":"http:\/\/kusuaks7\/?p=1303"},"modified":"2023-08-23T14:57:38","modified_gmt":"2023-08-23T14:57:38","slug":"data-scientists-are-thinkers","status":"publish","type":"post","link":"https:\/\/www.experfy.com\/blog\/bigdata-cloud\/data-scientists-are-thinkers\/","title":{"rendered":"Data Scientists Are Thinkers"},"content":{"rendered":"<h3 id=\"c42d\" name=\"c42d\" style=\"color:#aaa;font-style:italic;\"><strong>Execution vs. exploration and what it means for&nbsp;you<\/strong><\/h3>\n<p id=\"c618\" name=\"c618\">Data scientists serve a very technical purpose, but one that is vastly different from other individual contributors. Unlike engineers, designers, and project managers,&nbsp;data scientists are exploration-first, rather than execution-first.<\/p>\n<p id=\"c1d2\" name=\"c1d2\">This isn&rsquo;t a surprise when you consider the origin of data science. If you quickly look over the&nbsp;<a href=\"https:\/\/www.forbes.com\/sites\/gilpress\/2013\/05\/28\/a-very-short-history-of-data-science\/#ff5468255cfc\" rel=\"noopener noreferrer\" target=\"_blank\" class=\"broken_link\">early history<\/a>&nbsp;of the field, you see that things got started with academics researching the possibilities of computational statistics. This researcher-like mindset is still embedded in our DNA.<\/p>\n<p id=\"6431\" name=\"6431\">We are constantly surrounded by data that represents the business, product, and customers at scale. This allows us to see things from a 30,000-foot view, where other roles spend most of their time at ground-level, working on execution. It&rsquo;s important that we realize this fact, and more important that we make the most of it.<\/p>\n<h3 id=\"cebc\" name=\"cebc\"><strong>Execution vs. exploration<\/strong><\/h3>\n<p id=\"5b7b\" name=\"5b7b\">Most technical ICs within established companies focus on execution. This is pretty intuitive. In order for a company to be successful, it has to get things done that provide value.<\/p>\n<p id=\"1844\" name=\"1844\">Data science roles are a little different. They vary greatly depending on the team structure and size, but generally speaking, execution isn&rsquo;t where we&rsquo;re at our best. Our most valuable work often comes from exploration.<\/p>\n<p id=\"ea91\" name=\"ea91\">When it comes to complex questions and hypotheses, execution isn&rsquo;t the answer. Someone has to dive in and figure things out on a deeper level. They have to thoroughly analyze and explore the problem. Data scientists are the perfect candidates to take this on.<\/p>\n<p id=\"5a01\" name=\"5a01\">The act of thinking, coming up with a hunch, and then exploring that hunch is criminally&nbsp;<a href=\"https:\/\/towardsdatascience.com\/ode-to-the-type-a-data-scientist-78d11456019?source=friends_link&amp;sk=e17c9caff6432d53297b459953f4a09a\" target=\"_blank\" rel=\"noopener noreferrer\" class=\"broken_link\">underrated<\/a>. When done right, not only does this work produce interesting results\u200a&mdash;\u200ait drives&nbsp;<a href=\"https:\/\/towardsdatascience.com\/when-your-job-is-done-as-a-data-scientist-c5d887bb0d0e?sk=a347ca448076cf5fe35014cfd8d3cbe2\" target=\"_blank\" rel=\"noopener noreferrer\" class=\"broken_link\">decision-making<\/a>. This is where data scientists really thrive.<\/p>\n<p id=\"ba0c\" name=\"ba0c\">If you look at where certain roles end up on the execution-exploration spectrum, you get something like this:<\/p>\n<figure id=\"1346\" name=\"1346\">\n<p><canvas height=\"22\" width=\"75\"><\/canvas><img decoding=\"async\" data-src=\"https:\/\/cdn-images-1.medium.com\/max\/800\/1*bBwc6Qn7y3RdW_bUtSxTNw.png\" src=\"https:\/\/cdn-images-1.medium.com\/max\/800\/1*bBwc6Qn7y3RdW_bUtSxTNw.png\" style=\"width: 700px; height: 210px;\" \/><\/p>\n<\/figure>\n<p id=\"434f\" name=\"434f\">This isn&rsquo;t to say that data scientists can&rsquo;t or shouldn&rsquo;t execute. We spend a good amount of time building models, writing production code, and automating common tasks. The reality is that we have a diverse skill set that allows us to both explore and execute. This is why data scientists are hard to find, and also what makes the field so&nbsp;<a href=\"https:\/\/www.datacamp.com\/community\/blog\/what-is-data-science-exciting\" rel=\"noopener noreferrer\" target=\"_blank\" class=\"broken_link\">exciting<\/a>&nbsp;and challenging.<\/p>\n<h3 id=\"f1f2\" name=\"f1f2\"><strong>Finding a&nbsp;balance<\/strong><\/h3>\n<p id=\"35b3\" name=\"35b3\">Should data scientists go completely rogue and do whatever they want? Probably not. We can&rsquo;t blatantly ignore a backlog of JIRA tickets while looking into a hypothesis that came to mind at 2:00 AM the previous night. There has to be a balance here.<\/p>\n<p id=\"2c77\" name=\"2c77\">We have to be there for our stakeholders. This means delivering what they need in a timely manner so they can effectively make decisions and drive things forward.<\/p>\n<p id=\"1b21\" name=\"1b21\">However, we&rsquo;re&nbsp;<em>equally<\/em>&nbsp;obligated to take advantage of our unique position and analytical skill set. We do this by taking time to ponder new ideas, generate hypotheses, and wander through the data a little bit.<\/p>\n<p id=\"5174\" name=\"5174\">But the question remains: what does this look like in practice? It&rsquo;s not easy to think this way in a world of constant focus on execution. Recently, I&rsquo;ve been doing three different things to stay exploration-first. I&rsquo;m pretty happy with the results so far.<\/p>\n<h4 id=\"e856\" name=\"e856\"><strong>Block off&nbsp;time<\/strong><\/h4>\n<p id=\"268c\" name=\"268c\">First, I recommend blocking off an hour or so daily for deep thought and exploration. The best time for you will vary from person to person. I prefer first thing in the morning, but you could just as easily set aside an hour in the afternoon. It&rsquo;s extremely important to schedule this time.<\/p>\n<p id=\"387c\" name=\"387c\">Create a&nbsp;<a data-href=\"https:\/\/www.jotform.com\/blog\/setting-big-goals\/\" href=\"https:\/\/www.jotform.com\/blog\/setting-big-goals\/\" rel=\"noopener noreferrer\" target=\"_blank\">system<\/a>&nbsp;for success by making a recurring meeting with yourself every day. This is a meeting that you can&rsquo;t afford to miss or reschedule. Hold yourself accountable. This is your time to think.<\/p>\n<h4 id=\"2c8d\" name=\"2c8d\"><strong>Write everything down<\/strong><\/h4>\n<p id=\"5a03\" name=\"5a03\">In case you haven&rsquo;t heard, documentation is kind of important. Your thinking practice is no exception to this rule. No matter the quality of your idea, get it down somewhere. Create a running document or keep a notepad where you can allow these ideas, questions, and hypotheses to live on and be revisited.<\/p>\n<h4 id=\"e751\" name=\"e751\"><strong>Stay curious<\/strong><\/h4>\n<p id=\"e951\" name=\"e951\">As a data scientist, curiosity is your north star.&nbsp;Sometimes you&rsquo;ll get caught up in execution-mode and forget to develop and explore your own ideas. When this inevitably happens, curiosity is what will bring you back. I highly recommend this excellent article from Multithreaded for more on the topic of&nbsp;<a data-href=\"https:\/\/multithreaded.stitchfix.com\/blog\/2019\/01\/18\/fostering-innovation-in-data-science\/\" href=\"https:\/\/multithreaded.stitchfix.com\/blog\/2019\/01\/18\/fostering-innovation-in-data-science\/\" rel=\"noopener noreferrer\" target=\"_blank\">curiosity in data science<\/a>.<\/p>\n<blockquote id=\"da3d\" name=\"da3d\"><p>&ldquo;Empower your data scientists to come up with ideas you&rsquo;ve never dreamed of before.&ldquo;\u200a&mdash;\u200aEric&nbsp;Colson<\/p><\/blockquote>\n<h3 id=\"c118\" name=\"c118\"><strong>Shift your&nbsp;mindset<\/strong><\/h3>\n<p id=\"2117\" name=\"2117\">The execution-based work gets most of the love in data science. And can you blame us? It&rsquo;s easier to quantify. You can see the results that come from building a model or pushing code to production.<\/p>\n<p id=\"fa4e\" name=\"fa4e\">It&rsquo;s more difficult to see concrete results from an afternoon tinkering with a new idea. This new idea probably won&rsquo;t lead to anything significant. Maybe only 10% of these bets actually turn out to be anything. Don&rsquo;t let this discourage you. The 10% is worth it. The 10% is where the truly transformative work comes from\u200a&mdash;\u200aand it all starts with thinking.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Unlike engineers, designers, and project managers,&nbsp;data scientists are exploration-first, rather than execution-first. Data science roles are a little different. They vary greatly depending on the team structure and size, but generally speaking, execution isn&rsquo;t where they are at their best. Their most valuable work often comes from exploration. When it comes to complex questions and hypotheses, execution isn&rsquo;t the answer. Someone has to dive in and figure things out on a deeper level. They have to thoroughly analyze and explore the problem. Data scientists are the perfect candidates to take this on.<\/p>\n","protected":false},"author":553,"featured_media":2734,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"content-type":"","footnotes":""},"categories":[187],"tags":[94],"ppma_author":[3229],"class_list":["post-1698","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-bigdata-cloud","tag-data-science"],"authors":[{"term_id":3229,"user_id":553,"is_guest":0,"slug":"conor-dewey","display_name":"Conor Dewey","avatar_url":"https:\/\/secure.gravatar.com\/avatar\/?s=96&d=mm&r=g","user_url":"","last_name":"Dewey","first_name":"Conor","job_title":"","description":"<a href=\"https:\/\/www.linkedin.com\/in\/conordewey3\/\">Conor Dewey&nbsp;<\/a>is Data Scientist at Squarespace, an all-in-one content management system."}],"_links":{"self":[{"href":"https:\/\/www.experfy.com\/blog\/wp-json\/wp\/v2\/posts\/1698","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.experfy.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.experfy.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.experfy.com\/blog\/wp-json\/wp\/v2\/users\/553"}],"replies":[{"embeddable":true,"href":"https:\/\/www.experfy.com\/blog\/wp-json\/wp\/v2\/comments?post=1698"}],"version-history":[{"count":1,"href":"https:\/\/www.experfy.com\/blog\/wp-json\/wp\/v2\/posts\/1698\/revisions"}],"predecessor-version":[{"id":5877,"href":"https:\/\/www.experfy.com\/blog\/wp-json\/wp\/v2\/posts\/1698\/revisions\/5877"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.experfy.com\/blog\/wp-json\/wp\/v2\/media\/2734"}],"wp:attachment":[{"href":"https:\/\/www.experfy.com\/blog\/wp-json\/wp\/v2\/media?parent=1698"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.experfy.com\/blog\/wp-json\/wp\/v2\/categories?post=1698"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.experfy.com\/blog\/wp-json\/wp\/v2\/tags?post=1698"},{"taxonomy":"author","embeddable":true,"href":"https:\/\/www.experfy.com\/blog\/wp-json\/wp\/v2\/ppma_author?post=1698"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}