element14 Community
element14 Community
    Register Log In
  • Site
  • Search
  • Log In Register
  • About Us
  • Community Hub
    Community Hub
    • What's New on element14
    • Feedback and Support
    • Benefits of Membership
    • Personal Blogs
    • Members Area
    • Achievement Levels
  • Learn
    Learn
    • Ask an Expert
    • eBooks
    • element14 presents
    • Learning Center
    • Tech Spotlight
    • STEM Academy
    • Webinars, Training and Events
    • Learning Groups
  • Technologies
    Technologies
    • 3D Printing
    • FPGA
    • Industrial Automation
    • Internet of Things
    • Power & Energy
    • Sensors
    • Technology Groups
  • Challenges & Projects
    Challenges & Projects
    • Design Challenges
    • element14 presents Projects
    • Project14
    • Arduino Projects
    • Raspberry Pi Projects
    • Project Groups
  • Products
    Products
    • Arduino
    • Avnet Boards Community
    • Dev Tools
    • Manufacturers
    • Multicomp Pro
    • Product Groups
    • Raspberry Pi
    • RoadTests & Reviews
  • Store
    Store
    • Visit Your Store
    • Choose another store...
      • Europe
      •  Austria (German)
      •  Belgium (Dutch, French)
      •  Bulgaria (Bulgarian)
      •  Czech Republic (Czech)
      •  Denmark (Danish)
      •  Estonia (Estonian)
      •  Finland (Finnish)
      •  France (French)
      •  Germany (German)
      •  Hungary (Hungarian)
      •  Ireland
      •  Israel
      •  Italy (Italian)
      •  Latvia (Latvian)
      •  
      •  Lithuania (Lithuanian)
      •  Netherlands (Dutch)
      •  Norway (Norwegian)
      •  Poland (Polish)
      •  Portugal (Portuguese)
      •  Romania (Romanian)
      •  Russia (Russian)
      •  Slovakia (Slovak)
      •  Slovenia (Slovenian)
      •  Spain (Spanish)
      •  Sweden (Swedish)
      •  Switzerland(German, French)
      •  Turkey (Turkish)
      •  United Kingdom
      • Asia Pacific
      •  Australia
      •  China
      •  Hong Kong
      •  India
      •  Korea (Korean)
      •  Malaysia
      •  New Zealand
      •  Philippines
      •  Singapore
      •  Taiwan
      •  Thailand (Thai)
      • Americas
      •  Brazil (Portuguese)
      •  Canada
      •  Mexico (Spanish)
      •  United States
      Can't find the country/region you're looking for? Visit our export site or find a local distributor.
  • Translate
  • Profile
  • Settings
MusicTech
  • Challenges & Projects
  • Design Challenges
  • MusicTech
  • More
  • Cancel
MusicTech
Blog How to Write Your Design Challenge Blog Posts
  • Blog
  • Forum
  • Documents
  • Polls
  • Files
  • Mentions
  • Sub-Groups
  • Tags
  • More
  • Cancel
  • New
  • Share
  • More
  • Cancel
Group Actions
  • Group RSS
  • More
  • Cancel
Engagement
  • Author Author: spannerspencer
  • Date Created: 17 Mar 2016 10:44 AM Date Created
  • Views 2191 views
  • Likes 19 likes
  • Comments 14 comments
  • design challenge
  • blogging_challenge
  • blog_posts
  • writing
Related
Recommended

How to Write Your Design Challenge Blog Posts

spannerspencer
spannerspencer
17 Mar 2016

image

snowflake.gif

 

A few years ago I was one of 20 winners in a worldwide screen writing competition. Pretty cool eh?

 

The prize was 18 months of tuition and script development with an established screen writing tutor, which has paid no end of dividends. One of the many lessons that really stuck with me was about the writer's role within the film making team. He explained that a movie is the vision of literally hundreds of people -- not just the writer. He brought this up early as he's well aware that writers often feel that the movie is their vision alone.

 

But he did qualify this by saying that of those hundreds of visionary people, the writer is the only one who starts with nothing. Everyone else has your script to work from, and none of them ever have stare into the daunting abyss of a blank page.

 

Anyway, I was looking through our current Design Challenges, as I do most days, and I was put in mind of this valuable life lesson, as I know that many of you are currently facing the horror of a blank page, and might be wondering how to approach the not-insignificant number of blog posts that your Design Challenge requires. Fortunately, there are some excellent ways of approaching your writing requirements that will turn it into a task that's as enjoyable as building the project itself.

 

The Snowflake Method

Writing 15 blog posts is a daunting task. Where do you even begin? Getting started is hellishly difficult, and although it might sound contrary to good reason, having lots to say doesn't actually help with putting your first words down on paper (or on a screen, anyway). You'll invariably find that you feel like you're starting from the middle of the story.

 

Fortunately, the long-respected snowflake method is here to save the day. Don't start with a "Once upon a time..." and try to write your blog posts word by word. That's like trying to build a house by putting down bricks before you've drawn the blueprints.

 

  • Start with an outline that consists of nothing more than the title of each of your 15 Design Challenge blog posts. Once that list of titles is in front of you, you can rearrange and adjust them as needed very easily, and what you'll suddenly see is a bullet point list of your project. Spend a day on this, and let it settle overnight, at least. Congratulations! You now no longer have to worry about the blank page!
  • Expand each title into a short paragraph (absolutely no more than three sentences) that explains what will be in that specific blog post. As you work through all 15 titles, building them into very short paragraphs, you might want to go back and forth to adjust previous blog posts. What you'll find is that you're repeating steps within the blog posts, which is unnecessary work. Remove any repetitions, leaving that piece of information only in the most relevant blog post. Give it another 24 hours to settle, and then re-read it, and edit where needed.
  • Split each paragraph into its three sentences, and expand each sentence into its own paragraph. What you now have is the backbone of each of your 15 blog posts. Out of interest, you might be pleased to know that at this point you've now written more than half of your entire Design Challenge. How easy was that?
    • BEGINNING: What you have here are three sentences, representing the beginning, middle and end of the blog post. The beginning should introduce this specific blog post, and should be very short.
    • MIDDLE: The middle will be longer than both the beginning and end. Fill it with the work you actually did on this stage of the project and this stage alone! Don't be tempted to allude to what's coming in the next blog post, or to revisit what's already been covered in the previous one.
    • END: The end recaps exactly what stage the project is now at, and should be written as if the reader is following your instructions to make their own version of your project. When they read your short, closing paragraph, they should recognise their current project in your description. Again, don't be tempted to lead people into the next post! It's unnecessary, because the intro of your next blog post will do that.
  • Go back and re-read your blog posts, editing them as you go. Elaborate where necessary, and remove any and all repetitions, even if you don't want to -- just trust me on this one, and remove them. It might be hard, but do it.

 

And that's all there is to it. By building up your blog posts in this way, you'll never struggle about what to write, and the work load will feel massively lighter. In fact, you'll likely find yourself enjoying it a lot more than expected!

 

Building as You Write

Flickr_-_Official_U.S._Navy_Imagery_-_An_electronics_engineer_uses_visible_lasers_to_align_various_optical_components..jpgEmploying the snowflake method in your Design Challenge requires a slight adjustment on how a writer would use it. You see, you're building the project as you go, and there's no need to have all 15 blog posts written before you post the first one.

 

But you can use the snowflake as a valuable part of your project planning, too. Go back to your snowflake outline (the 15 blog post titles) and add a short parenthesis that covers the project build at each stage. This is only for you to read, so don't spend too long editing or rewriting. You should find that the build instructions mesh beautifully with your blog post titles. If they don't, rewrite the titles and adjust your project plan here and there until they do.

 

One will feed into the other, and the snowflake will suddenly help you massively when it comes to putting your parts together. It'll even give you a timeline of how long things are going to take.

 

Now go back to the snowflake, and expand the titles into paragraphs before starting work on building your project.

 

What you now have are the train tracks of your Design Challenge. One track is the blog posts, and the other is the project. They're running perfectly parallel to each other, and as you finish a milestone in your build (and you'll instinctively know where those milestones are, thanks to the outline) you can take a break by expanding the three sentences into the full post. When you've done enough writing (which will now be a much quicker job than you ever expected) you can break off, go back to building, do a bit of testing, or take some photos.

 

Say it With a Picture

As you know from seeing other people's posts, photos and videos are a superb way to get your message across. A single photo can remove a wall of text, and a video can replace a mosaic of photos.

 

You can't include too many, so go nuts with these. Just follow the same rules as when writing: No repetition, and don't feel the need to over explain what's in your photos and videos within your blog post. People have eyes, and can see what's in them -- you don't need to go into lots of depth about an upcoming photo. Give your readers enough credit to understand them.

 

Follow this method in your Design Challenge, and you'll be amazed at how quickly your tasks get done. And when they don't even feel like work, all that's left is a sense of enjoyment around every aspect. You'll have found as much pleasure in writing up your project as you did in building it, and that'll only make you more enthusiastic about getting straight into your next build!

 

So good luck to our current Design Challengers, and please join me in a round of applause as we eagerly await their epic blog posts!

  • luiszayas
  • carmelito
  • agerber
  • liamtmlacey
  • flec8
  • a.soria
  • selement14
  • momososo
  • msimon16
  • fraktalize
  • tpwhiteco
  • hmudesign
  • elliot.tanner
  • lexbryan
  • Sign in to reply

Top Comments

  • mcb1
    mcb1 over 9 years ago +3
    Nice write-up Spanner. There should be no excuses for missing blogs. I did the outline for my Forget Me Not challenge and as things changed during the challenge the list got slightly re-arranged. I found…
  • dougw
    dougw over 9 years ago +3
    Good topic - excellent method of fleshing out a report. I never heard of it described as a snowflake before, although it is appropriate. I have heard it called a tree structure, where each branch grows…
  • DAB
    DAB over 9 years ago +2
    I use a variant of the systems development process for planning my writing. Assess the requirements/goals of the article. Define a structure for information flow. Establish an outline. Write the summary…
Parents
  • mcb1
    mcb1 over 9 years ago

    Nice write-up Spanner.

    There should be no excuses for missing blogs.

     

    I did the outline for my Forget Me Not challenge and as things changed during the challenge the list got slightly re-arranged.

    I found it helped to make sure I didn't get side-tracked onto things that were not necessary just then.

     

    The important part is to have a plan.

    You can modify the plan as circumstances change, and it's still a plan.

     

     

    Mark

    • Cancel
    • Vote Up +3 Vote Down
    • Sign in to reply
    • More
    • Cancel
Comment
  • mcb1
    mcb1 over 9 years ago

    Nice write-up Spanner.

    There should be no excuses for missing blogs.

     

    I did the outline for my Forget Me Not challenge and as things changed during the challenge the list got slightly re-arranged.

    I found it helped to make sure I didn't get side-tracked onto things that were not necessary just then.

     

    The important part is to have a plan.

    You can modify the plan as circumstances change, and it's still a plan.

     

     

    Mark

    • Cancel
    • Vote Up +3 Vote Down
    • Sign in to reply
    • More
    • Cancel
Children
  • spannerspencer
    spannerspencer over 9 years ago in reply to mcb1

    Mark Beckett wrote:

     

    The important part is to have a plan.

    You can modify the plan as circumstances change, and it's still a plan.

    This is a really important aspect, I think. It's easy to become a slave to your original plan. It should be considered a living document, that remains fluid, flexible and agile. Let it change as it needs to when the work begins.

     

    As you say Mark, it's still a plan even though it changes and adapts.

     

    Excellent point, well made.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • More
    • Cancel
  • DAB
    DAB over 9 years ago in reply to spannerspencer

    Often, it is the planning process, not the actual plan that is important.

    As you go through the process you consciously identify issues and concerns and decide if they should be tracked as risks and identify decision points for alternatives.

     

    Executing the plan becomes much easier if you have this information documented and your evaluation criteria or event points preplanned.

     

    It makes it much easier to make quick decisions when events go against your original plan and you need to go to option B or C.

     

    It also makes it easier to discuss the issues with the customer when you keep them appraised of the issues and decisions.

     

    DAB

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • More
    • Cancel
element14 Community

element14 is the first online community specifically for engineers. Connect with your peers and get expert answers to your questions.

  • Members
  • Learn
  • Technologies
  • Challenges & Projects
  • Products
  • Store
  • About Us
  • Feedback & Support
  • FAQs
  • Terms of Use
  • Privacy Policy
  • Legal and Copyright Notices
  • Sitemap
  • Cookies

An Avnet Company © 2025 Premier Farnell Limited. All Rights Reserved.

Premier Farnell Ltd, registered in England and Wales (no 00876412), registered office: Farnell House, Forge Lane, Leeds LS12 2NE.

ICP 备案号 10220084.

Follow element14

  • X
  • Facebook
  • linkedin
  • YouTube