Kickstarter Literacy Revision Proposal

Background:

My piece will essentially go through a detailed list of things a Kickstarter project creator and/or project must do in order to have connection literacy, one of the literacies I descried in my midterm project.

Audience:

I will be writing my midterm revision for an audience that consists of newbie Kickstarter project creators. Specifically, I will be aiming at the population of young, 20-30 year old college grads hoping to get into the startup business. That particular audience would be interested in my project because they probably would appreciate any tips on getting ahead in the highly competitive startup field.

I decided to not specify design/tech projects in my revision because most people interested in the startup industry are creating startups based around design/tech products anyway. It’d be redundant for me to indicate that my article is more useful for design and technology project creators.

I am choosing to focus on connection literacy because college grads often have not been taught on how they should interact with people who have the money (and therefore power). No matter how good a college grad is at engineering a new product, that person will not be successful if he/she cannot talk to potential investors in a way that would make the investor interested in supporting the grad. I would probably post my finished article on a website that targets college-age people and hosts opinion articles.

Key Questions:

What is connection literacy in the context of Kickstarter?
Why do I need connection literacy in order to be a successful project creator?
How do I obtain connection literacy?

Writerly Challenges and Concrete Goals

Goal 1: Keep well-organized headers/titles when I write my revision and use at most one bold point per heading.
This two-fold goal is worth working towards because I will be able to make sure that I keep my thoughts in line as well as prevent an overload of information. While I was writing my midterm, I kept changing my mind as to what I wanted to write, but having an organizational structure set up beforehand let me bring in my new ideas and integrate them in with my existing points. I definitely want to take the same mindset with my to my midterm revision. In fact, I think keeping that mindset will be more important for me in my revision because I want it to be a much more focused and directive piece than my midterm was.

However, one problem with my midterm was that I used bold text too frequently. My midterm had several lines of bolded text under each heading, often stuck in the middle of the paragraph. While I intended to emphasize certain points with my bold text, I only ended up confusing my readers on what I was trying to say with each section and distracting them from my piece as a whole. Having only one bold line per heading will make my formatting less of a distraction and more of a guideline on what to take away from each section.

If I’m successful with this, my revised midterm will have nice headers and paragraph structure just like my midterm. It should be even easier to read through because there will be less distractions from formatting. I don’t really see a case where I’d fail because I always write out my organizational structure before I start writing any piece or add them as I write my piece because I like the feeling of being organized. If I end up with more than one bold line per heading, I’d just create a new heading with the second line of bold text because I’d know I have too much information for one section of the piece.

Goal 2: Make sure my tone is semi-professional; the audience should feel like they are sitting in a small room in a circle with me giving a presentation.
I chose this goal because I want to make sure that my audience doesn’t feel alienated by my piece. Literacies can be very dense and difficult to explain, so by making sure I keep a semi-professional tone, I can make sure that I give an adequately formal explanation of my opinion while keeping my audience’s attention.

If I’m successful, I should be able to hand my piece to any of my peers and see them read through the piece without feeling bored or overwhelmed by information. If I fail, however, I’d probably see a lot of confused faces because people would feel intimidated if I started to use more complex language.

Goal 3: Make sure that I use at least 2 examples for each of my points regarding connection literacy – one example from a successful Kickstarter project and one example from a failed Kickstarter project.
One of the problems of my midterm piece was that I was only able to incorporate one example to support my points. I had so much information that using even more examples probably would have overwhelmed my readers or make my piece too long to read in one siting. Since my revision is more focused, using more examples make sense because I can draw from a couple of specific points of each example to support my points.

If I’m successful, readers will feel satisfied after reading my piece. They shouldn’t have any doubts as to whether what I’m saying is correct because they’ll see examples of both successes and failures. If not, then my readers will probably be left yearning for more or doubting me because they won’t have seen enough examples.

Genre Model:

I envision my piece to be essentially the transcription of a hypothetical lecture and/or Prezi/Keynote/PowerPoint presentation I’d give on connection literacy in Kickstarter, slightly modified to fit an online blog format. I don’t think there’s any online blog with articles that follow the exact genre I’m envisioning (I’m not sure if there’s a name for it). I want to emulate something of a cross between The Last Lecture by Randy Pausch (the book) and any Gizmodo article that provides some technical explanation - this article, for example. I want to keep the best of both worlds – the detail allowed in a long lecture or book as well as the organizational tools available to online bloggers.

Unless otherwise stated, the content of this page is licensed under Creative Commons Attribution-ShareAlike 3.0 License