<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Digital Futures on Medium]]></title>
        <description><![CDATA[Stories by Digital Futures on Medium]]></description>
        <link>https://medium.com/@Digital-Futures?source=rss-299a447e1c32------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*Wx4dtI4wU5Cj2y8V0e_xKA.png</url>
            <title>Stories by Digital Futures on Medium</title>
            <link>https://medium.com/@Digital-Futures?source=rss-299a447e1c32------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 11:07:16 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@Digital-Futures/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Showing off your hard work]]></title>
            <link>https://medium.com/digital-futures-publications/showing-off-your-hard-work-dad65cc732c4?source=rss-299a447e1c32------2</link>
            <guid isPermaLink="false">https://medium.com/p/dad65cc732c4</guid>
            <category><![CDATA[data-science]]></category>
            <category><![CDATA[machine-learning]]></category>
            <category><![CDATA[data-analysis]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[communication]]></category>
            <dc:creator><![CDATA[Digital Futures]]></dc:creator>
            <pubDate>Fri, 03 Dec 2021 16:46:43 GMT</pubDate>
            <atom:updated>2021-12-03T16:46:43.069Z</atom:updated>
            <content:encoded><![CDATA[<p>Congratulations, you’ve completed a project! Now it’s time to let the world know how much of a great job you’ve done. Check out our framework for documenting a data science project.</p><p>By publishing your work, you will contribute to building your online persona as a great data scientist — you can think of this as building your own personal data science brand. Once published; people can read, comment, and applaud your work. Having a published portfolio acts as a passive investment for improving your networking — you never know who will be reading your pieces.</p><p>The main objective of publishing an article will be to demonstrate your thought process:</p><ul><li>Identifying a problem</li><li>Stating the importance of solving this problem</li><li>Documenting the methodology</li><li>Curating relevant results</li><li>Creating actionable insights</li></ul><p>Our framework is designed to format your project in a gripping and efficient manner for readers. The document should start broad and end narrow, think of the narrative as a funnel…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/910/1*xAi59buDiCN3jNxlx9QX0w.png" /><figcaption>Narrative funnel</figcaption></figure><h3>Introduction</h3><p>Your introduction is about setting the scene with domain knowledge. Data scientists &amp; analysts should excel at storytelling, and we do this by tailoring to our audience. The main points to get across during section are as follows:</p><ol><li>What is the motivation for this project?</li><li>Announce the problem statement</li></ol><ul><li>What is the problem you will tackle?</li><li>Who or what is affected by this problem?</li><li>Why is it important to solve?</li></ul><p>3. What are the benefits for solving this problem?</p><p>4. Breakdown your problem into major concepts</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qBP6gp2k-029kYsT1gm5UA.jpeg" /><figcaption>Planning by <a href="https://unsplash.com/@kvalifik?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Kvalifik</a> on <a href="https://unsplash.com/s/photos/writing-on-window?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><h3>Solution</h3><p>Here you will give a broad overview of how you will solve the problem statement above. Whether you use data analysis to tell a story or build a machine learning model for predictions, a two-sentence summary of the approach will set the scene for the technical solution that will follow.</p><h4>Technical Solution</h4><p>The technical solution can be broken down into 3 components:</p><ol><li>Overview of the dataset</li></ol><ul><li>What does the data describe?</li><li>Why this/these datasets specifically?</li><li>Where did you find the resources?</li></ul><p>2. State the cleaning process and your rationale behind these steps?</p><p>3. What columns/characteristics of the dataset are most interesting and why?</p><p>If you have an analysis-based project start with a broad exploratory analysis and build a narrative through insights gained from data. You should be thinking about drilling down with each analytical step until clear distilled actionable insights have been found.</p><ul><li>Always incorporate tables, charts and key statistics when drilling down with each step</li><li>What does the data tell you at each step? Are there any underlying patterns? Use these patterns to flow into the next analytical question</li><li>As a tip for narrative “glue”- use the mindset of- “what is the answer” and “why is this the answer?”</li></ul><p>If your project is machine learning based:</p><ul><li>Describe your methodology and rationale behind: feature engineering, model selection etc</li><li>What metrics are you using? This is critical, why are you using these particular metrics, are there any potential risks with using this metric?</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9rBUPbUegzllFWJsjJeo0g.jpeg" /><figcaption>Analysing results by <a href="https://unsplash.com/@uxindo?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">UX Indonesia</a> on <a href="https://unsplash.com/s/photos/analysis?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><h3>Results</h3><p>Even if you did not reach your desired outcome, it’s important to document the overall results. Data science has shown a rapid evolution over the past five years, this can be derived from documenting not just the success stories, but the dead ends as well.</p><ul><li>Did your analysis explain the problem?</li><li>How did your analysis help solve the problem?</li><li>What does a well performing model look like?</li><li>Did your model achieve this?</li><li>Are there comparable scores or benchmarks already publicly available?</li><li>View your performance from another angle- try using a variety of metrics or a confusion matrix</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7IpvXRXAIgwg_DE7ruOM0g.jpeg" /><figcaption>Magnifying glass by <a href="https://unsplash.com/@markuswinkler?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Markus Winkler</a> on <a href="https://unsplash.com/s/photos/magnifying-glass?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><h3>Limitations</h3><p>Think of this section as a place to highlight areas for optimisation- How would you be critical of your own approach?</p><ul><li>Did you have enough data?</li><li>Did this data best reflect the problem?</li><li>Did you introduce noise when cleaning?</li><li>Was there bias in the dataset?</li><li>Does speed matter? Is inference too slow?</li><li>Error analysis- were there any themes in the mistakes made at the time of prediction?</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jkL781LTplk4M2_R9xHhaw.jpeg" /><figcaption>Product roadmap by <a href="https://unsplash.com/@slidebean?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Slidebean</a> on <a href="https://unsplash.com/s/photos/product-roadmap?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><h3>Next steps</h3><h4>Improvements</h4><p>How would you improve or fix the limitations? Try and phrase this sub-section as if you were to give advice to yourself or someone else tackling a similar problem.</p><ul><li>What have you learnt about the process of the project?</li><li>How would you improve the project if you had to repeat it again?</li><li>If you had more time, what would you do?</li></ul><h4>Future thoughts</h4><p>This sub-section demonstrates that you are forward-looking and can see the big picture.</p><ul><li>Where could this project go next?</li><li>Are there any other fields that your solution could be applied to?</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CKCAz6sNnZMwcoGjIVmQLw.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@smartworkscoworking?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Smartworks Coworking</a> on <a href="https://unsplash.com/s/photos/teamwork?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><h3>Summary</h3><p>Distil the entire project into a single paragraph.</p><ul><li>What was the problem?</li><li>Why did you try and solve the problem?</li><li>What was the solution?</li><li>What was the result?</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lFGIHuLOQr61410Ofbslaw.jpeg" /><figcaption>Measuring tape by <a href="https://unsplash.com/@diana_pole?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Diana Polekhina</a> on <a href="https://unsplash.com/s/photos/tailor?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><h3>Style guide</h3><h4>Audience</h4><p>Thinking about your audience is fundamental when relaying information, be that an article, presentation, or daily stand-up. Each audience will have a different technical understand and different angles that need addressing. For the purpose of these articles, you will be writing for an audience that contains one data science colleague and one stakeholder.</p><h4>Title</h4><p>A title should be eye catching and concise. Think about the title at the end once you’ve written the story, this will usually give inspiration.</p><h4>Formatting</h4><p>Include headers for the main components- Introductions, Solution, Results etc and sub-headers for sections within main components e.g. Improvements, Future Thoughts etc.</p><h4>Images</h4><p>Use images and diagrams to summaries thoughts and represent concepts and workflows.</p><ul><li>Use <a href="https://unsplash.com/">unsplash</a> for free stock images and ensure you reference the creator within your article</li><li><a href="https://miro.com/app/dashboard/">miro</a> and <a href="https://app.diagrams.net/">draw.io</a> can be effective tools for drawing diagrams</li></ul><h4>Video or gifs</h4><p>Videos and gifs can be a great way to explain or aid in describing concepts or even showing results eg. This post shows off real-time predictions of <a href="https://medium.com/@ageitgey/machine-learning-is-fun-part-4-modern-face-recognition-with-deep-learning-c3cffc121d78">machine learning</a></p><h4>Charts and visualisations</h4><p>Check out these links for what makes a good visualisation</p><ul><li><a href="https://www.informationisbeautiful.net/visualizations/what-makes-a-good-data-visualization/">Information is Beautiful</a></li><li><a href="https://www.columnfivemedia.com/25-tips-to-upgrade-your-data-visualization-design/">25 tips to upgrade your data visualisations design</a></li></ul><h4>Links</h4><p>Just like we demonstrated above, if a source already exists about a specific topic that aids your narrative- use it and give credit.</p><h4>Code</h4><p>Medium offers the ability to embed code directly into an article, this is great way to add variety to your narrative and to show off any interesting code you’ve written. Links to your project code should be hosted as part of your portfolio, be sure to check out <a href="https://github.com/">github</a> repositories.</p><h4>Final words</h4><p>The final lines of your article should be a thank you to your readers and a link to your project code, Linkedin, twitter and website.</p><h3>Thanks for your time</h3><p>Thanks for reading our post on how to really shine when documenting a project. Everyone puts in so much time and effort into solving problems, it’s important that the work is not only recognised but available for others to build upon.</p><p>At <a href="https://digitalfutures.com/">Digital Futures</a> we believe that talent is distributed equally but opportunity is not. We are open to all — check out all of our free content here and join the conversation.</p><p>And if you think this is good, imagine what our Academy is like! Find out more about all of our programmes <a href="https://digitalfutures.com/for-individuals/academy/">here</a> and start your Digital Future.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dad65cc732c4" width="1" height="1" alt=""><hr><p><a href="https://medium.com/digital-futures-publications/showing-off-your-hard-work-dad65cc732c4">Showing off your hard work</a> was originally published in <a href="https://medium.com/digital-futures-publications">Digital-Futures-Publications</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>