IMPROVE YOUR WRITING WITH GRAMMAR.NET’S GRAMMAR CHECKER FOR FREE


 

With Grammar.net’s Grammar Checker you can check and correct grammar and spelling mistakes and use Thesaurus feature to find synonyms.

It’s easy to check your texts using our Grammar Checker – just download this Free program. Then you need to highlight the text you want to check and press CTRL+G button. Or use Grammar.net’s Rich Text for editing and checking your text with rich mark-up, just copy-paste it and then check your text. Leer más “IMPROVE YOUR WRITING WITH GRAMMAR.NET’S GRAMMAR CHECKER FOR FREE”

Anuncios

The Magazine Issues in New Era of Writing | theindustry.cc


It’s not very often that a product or service redefines the market in which it resides. However, Marco Arment has done exactly that with his latest project, The Magazine. The Magazine is a subscription-based application that delivers stories; stories that bring technology and writing to a crossroad. Marco specifically states in his foreword, though, that at times it will go beyond technology at times when he feels it fits his vision for The Magazine.

The Magazine 01 The Magazine Issues in New Era of Writing

Writing

Arment’s unique vision delivers these stories in a beautiful design, while being wonderfully written by a grand curation of writers.

Rather than telling readers everything that happens in technology, we deliver meaningful editorial and big-picture articles.

Full history
http://theindustry.cc/2012/10/16/the-magazine-issues-in-new-era-of-writing/

10 Tips on Writing from David Ogilvy | de los tipos que rompieron el molde…


http://bit.ly/LF9w3t

by  | brainpickings.org

“Never write more than two pages on any subject.”

How is your new year’s resolution to read more and write better holding up? After tracing the fascinating story of the most influential writing style guide of all time and absorbing advice on writing from some of modern history’s most legendary writers, here comes some priceless and pricelessly uncompromising wisdom from a very different kind of cultural legend: iconic businessman and original “Mad Man” David Ogilvy. On September 7th, 1982, Ogilvy sent the following internal memo to all agency employees, titled “How to Write”:

The better you write, the higher you go in Ogilvy & Mather. People who think well, write well.

Woolly minded people write woolly memos, woolly letters and woolly speeches.

Good writing is not a natural gift. You have to learn to write well. Here are 10 hints:

1. Read the Roman-Raphaelson book on writing. Read it three times.

2. Write the way you talk. Naturally.

3. Use short words, short sentences and short paragraphs.

4. Never use jargon words like reconceptualize,demassificationattitudinallyjudgmentally. They are hallmarks of a pretentious ass.

5. Never write more than two pages on any subject.

6. Check your quotations.

7. Never send a letter or a memo on the day you write it. Read it aloud the next morning — and then edit it.

8. If it is something important, get a colleague to improve it.

9. Before you send your letter or your memo, make sure it is crystal clear what you want the recipient to do.

10. If you want ACTION, don’t write. Go and tell the guy what you want.

David Leer más “10 Tips on Writing from David Ogilvy | de los tipos que rompieron el molde…”

The 4 Keys to Writing Persuasive Copy Without Hype, BS, or Other Icky Gimmicks

How to write conversationally

Don’t write—tell. The best way to get started is not to write at all—but to speak.

Ideally, record yourself talking about your topic with a friend you know and trust. That way, you’ll avoid most of the self-consciousness that comes when you get out a voice recorder and try to record yourself talking to the air.

Then play back your recording and just listen to what you say. Take notes. How do your sentences sound? How often do you break the rules of formal grammar? I bet it’s all the time. So forget formal grammar. How often do you say something that in retrospect sounds totally gitty? Pretty often too, probably. So figure out what you wish you’d said, and use that instead. Write like you talk, but with the benefit of lots of time to choose your words. It’ll be a lot easier to read—because people read with an internal monologue. When you write conversationally, they can hear your words flow.


 

http://blog.kissmetrics.com


 

You should already know that clarity trumps persuasion for making sales. In fact, to borrow a metaphor from direct-response expert Dean Rieck, your copy should be like a shop window—completely invisible, affording a perfect view of the thing you’re selling.

But as with most important things in life, that’s easier said than done.

Fortunately—as with most things in life—much of the mystery can be removed by adopting a system that takes care of the basics. So let me introduce you to my Four Keys for writing clear, shiny copy that affords prospects the perfect view of whatever it is you’re selling.

Key #1: Conversational style

I’m sure you’ve heard it said that people don’t buy from websites—they buy from people.

And I’m sure you’ve also heard that people seldom buy from people they don’t like and trust.

Which is why hyped highlighter copy doesn’t tend to work. There’s no real personal connection, because it doesn’t read like anything a person would say—certainly not a person you’d be inclined to like or trust.

The same goes for verbose, puffed-up “corporatese”. No one talks like that—and if they did we’d assume there was something ludicrously wrong with them.

The solution is to write like you would talk.

Simple, right? So simple you probably reckon there’s no need to read the rest of this section—but you’d be wrong.

Because actually, writing like you talk is hard, and you’ll likely fail at it to start with. That’s because you have to make a shift in your thinking before it will click for you.

You have to get out of “Writing Mode”… Leer más “The 4 Keys to Writing Persuasive Copy Without Hype, BS, or Other Icky Gimmicks”

Proposal Writing

I work at a Web development company and we’ve experimented with proposal writing a lot over the years. We’ve seen the good and the bad, and we have found something better. In this article I will share the pains that we have experienced in the proposal writing process, the solution we adopted, and our process for carrying out that solution. I’ll also give you guidelines to help you know when this solution is and isn’t appropriate.

Proposal Writing Causes Pain
After several years of writing proposals, we began to notice that something wasn’t right. As we considered the problem we noticed varying levels of pain associated with the proposal writing process. We categorized those pains as follows:

The Rush
Getting a proposal done was usually about speed. We were racing against the clock and working hard to deliver the proposal as efficiently and as effectively as possible. However, sometimes corners would get cut. We’d reuse bits and pieces from older proposals, checking and double-checking for any references to the previous project. While the adrenaline helped, the rush gets old because you know that, deep down, it’s not your best work. Besides, you don’t even know if you’re going to close the deal, which leads to the next pain.

The Risk
Our proposal close ratio with clients that came directly to us was high. We’d work hard on the proposals and more often than not, we’d close the deal. The risk was still there, however, and I can think of several proposals that we had spent a lot of time and effort on for a deal that we didn’t get. Not getting the deal isn’t the problem — the problem is going in and investing time and energy in a thorough proposal without knowing if there is even the likelihood that you’re going to close the deal.
The Details
The difference between a project’s success and its failure is in the details. In proposal writing, the details are in the scope. What work is included, what is not, and how tight is the scope? Now, this is where the “rush” and the “risk” play their part. The rush typically causes us to spend less time on details and the “risk” says: “Why spell it all out and do the diligence when you might not even get the project?” A self-fulfilling prophecy, perhaps, but a legitimate concern nonetheless. Selling a project without making the details clear is asking for scope creep, and turns what started out as a great project into a learning experience that can last for years.
Now, writing is an important part of the project and I’m not about to say you shouldn’t write. Having a written document ensures that all parties involved are on the same page and completely clear on exactly what will be delivered and how it will be delivered. What I’m saying, though, is that you should stop writing proposals.


By  | http://www.smashingmagazine.com

After several grueling days I had finally finished the proposal. I sent it off and waited for a response. Nothing. After a few weeks, I discovered that they were “just looking”. Despite the urgency and aggressive timeline for the RFP (Request For Proposal) plus the fact that we had done business with this organization before, the project was a no-go. My days of effort were wasted. Not entirely, though, because the pain of that loss was enough to drive me to decide that it wouldn’t happen again.

I work at a Web development company and we’ve experimented with proposal writing a lot over the years. We’ve seen the good and the bad, and we have found something better. In this article I will share the pains that we have experienced in the proposal writing process, the solution we adopted, and our process for carrying out that solution. I’ll also give you guidelines to help you know when this solution is and isn’t appropriate.

Proposal Writing Causes Pain

After several years of writing proposals, we began to notice that something wasn’t right. As we considered the problem we noticed varying levels of pain associated with the proposal writing process. We categorized those pains as follows:

  • The Rush
    Getting a proposal done was usually about speed. We were racing against the clock and working hard to deliver the proposal as efficiently and as effectively as possible. However, sometimes corners would get cut. We’d reuse bits and pieces from older proposals, checking and double-checking for any references to the previous project. While the adrenaline helped, the rush gets old because you know that, deep down, it’s not your best work. Besides, you don’t even know if you’re going to close the deal, which leads to the next pain.
  • The Risk
    Our proposal close ratio with clients that came directly to us was high. We’d work hard on the proposals and more often than not, we’d close the deal. The risk was still there, however, and I can think of several proposals that we had spent a lot of time and effort on for a deal that we didn’t get. Not getting the deal isn’t the problem — the problem is going in and investing time and energy in a thorough proposal without knowing if there is even the likelihood that you’re going to close the deal.
  • The Details
    The difference between a project’s success and its failure is in the details. In proposal writing, the details are in the scope. What work is included, what is not, and how tight is the scope? Now, this is where the “rush” and the “risk” play their part. The rush typically causes us to spend less time on details and the “risk” says: “Why spell it all out and do the diligence when you might not even get the project?” A self-fulfilling prophecy, perhaps, but a legitimate concern nonetheless. Selling a project without making the details clear is asking for scope creep, and turns what started out as a great project into a learning experience that can last for years.

Now, writing is an important part of the project and I’m not about to say you shouldn’t write. Having a written document ensures that all parties involved are on the same page and completely clear on exactly what will be delivered and how it will be delivered. What I’m saying, though, is that you should stop writing proposals.

Write Evaluations, Not Proposals

Write Evaluations, Not Proposals — And Charge For Them… Leer más “Proposal Writing”

Do Short Posts Deliver on Value?

I write long.

It’s a bit of a fault of mine, actually. I feel that long posts are just … better, somehow. Fuller. Richer. More valuable. I feel that long posts give you all the goods, everything you need, all in one place.

Long posts are hard work, though. Delivering that much value and information in a single post without losing a reader’s attention is tough. And if a reader decides it’s too much work to get to the end…

Well. That’s no good, is it? Then nothing gets read. All that hard work goes to waste.

So each time I write blog posts, I’m mindful of my tendency to write long. Sometimes my first drafts extend well over 1,500 words. Then I trim and edit and cut and snip until they’re back down to something manageable.

Truth be told, that isn’t always fun.

In fact, some people have asked that I shorten posts down. That I deliver fast bites with impact, that I publish quick messages they can grasp in an instant. They want to hear what I have to say… they just don’t have the time to read it all.

This isn’t new. Other thought leaders write short. Chris Brogan publishes posts that are just a few paragraphs. Not always, but sometimes. Seth Godin has mastered the short post and his audience loves him for it. Julien’s posts get straight to the point.

And it works…


Written by Jameshttp://menwithpens.ca/ 

I write long.

It’s a bit of a fault of mine, actually. I feel that long posts are just … better, somehow. Fuller. Richer. More valuable. I feel that long posts give you all the goods, everything you need, all in one place.

Long posts are hard work, though. Delivering that much value and information in a single post without losing a reader’s attention is tough. And if a reader decides it’s too much work to get to the end…

Well. That’s no good, is it? Then nothing gets read. All that hard work goes to waste.

So each time I write blog posts, I’m mindful of my tendency to write long. Sometimes my first drafts extend well over 1,500 words. Then I trim and edit and cut and snip until they’re back down to something manageable.

Truth be told, that isn’t always fun.

In fact, some people have asked that I shorten posts down. That I deliver fast bites with impact, that I publish quick messages they can grasp in an instant. They want to hear what I have to say… they just don’t have the time to read it all.

This isn’t new. Other thought leaders write short. Chris Brogan publishes posts that are just a few paragraphs. Not always, but sometimes. Seth Godin has mastered the short post and his audience loves him for it. Julien’s posts get straight to the point.

And it works… Leer más “Do Short Posts Deliver on Value?”

Do Short Posts Deliver on Value?

So each time I write blog posts, I’m mindful of my tendency to write long. Sometimes my first drafts extend well over 1,500 words. Then I trim and edit and cut and snip until they’re back down to something manageable.

Truth be told, that isn’t always fun.

In fact, some people have asked that I shorten posts down. That I deliver fast bites with impact, that I publish quick messages they can grasp in an instant. They want to hear what I have to say… they just don’t have the time to read it all.

This isn’t new. Other thought leaders write short. Chris Brogan publishes posts that are just a few paragraphs. Not always, but sometimes. Seth Godin has mastered the short post and his audience loves him for it. Julien’s posts get straight to the point.

And it works. [Más…]

I’ve always thought that short posts were the cheap way out, honestly, which is why I suppose I developed the habit of writing long. I thought short posts were a cop-out. That somehow, they didn’t deliver value. That they lacked in substance or that the author couldn’t be bothered to write and just tossed it off.

But I’m beginning to think a little differently about short posts.

It would feel relieving to slam out a fast, impactful, thought-provoking message as it struck me than have to reserve hours out of my week to craft and hone those long posts into reader-worthy length. It would be better, too, because I have a lot to say, and I could say more of it if writing wasn’t such a time-consuming chore.

Don’t get me wrong. I like writing. And I like writing long.

But I’m no longer sure it’s necessary – at least, not for every post.

Would you prefer to read something that’s really good that doesn’t take forever to read? I know I do when I visit other blogs – we’re all busy, after all.


I write long.

It’s a bit of a fault of mine, actually. I feel that long posts are just … better, somehow. Fuller. Richer. More valuable. I feel that long posts give you all the goods, everything you need, all in one place.

Long posts are hard work, though. Delivering that much value and information in a single post without losing a reader’s attention is tough. And if a reader decides it’s too much work to get to the end…

Well. That’s no good, is it? Then nothing gets read. All that hard work goes to waste.

So each time I write blog posts, I’m mindful of my tendency to write long. Sometimes my first drafts extend well over 1,500 words. Then I trim and edit and cut and snip until they’re back down to something manageable.

Truth be told, that isn’t always fun.

In fact, some people have asked that I shorten posts down. That I deliver fast bites with impact, that I publish quick messages they can grasp in an instant. They want to hear what I have to say… they just don’t have the time to read it all.

This isn’t new. Other thought leaders write short. Chris Brogan publishes posts that are just a few paragraphs. Not always, but sometimes. Seth Godin has mastered the short post and his audience loves him for it. Julien’s posts get straight to the point.

And it works. Leer más “Do Short Posts Deliver on Value?”