Empirically, the way to do really big things seems to be to start with deceptively small things. Want to dominate microcomputer software? Start by writing a Basic interpreter for a machine with a few thousand users. Want to make the universal web site? Start by building a site for Harvard undergrads to stalk one another.
...
I think the way to use these big ideas is not to try to identify a precise point in the future and then ask yourself how to get from here to there, like the popular image of a visionary. You'll be better off if you operate like Columbus and just head in a general westerly direction. Don't try to construct the future like a building, because your current blueprint is almost certainly mistaken. Start with something you know works, and when you expand, expand westward.
The popular image of the visionary is someone with a clear view of the future, but empirically it may be better to have a blurry one.
----
Paul Graham, on Frighteningly Ambitious Start-up Ideas.
Isn't that funny that even the metaphor we use for such kind of stuff is some yahoo that got the radius of Earth wrong and survived just by accident?
Full-disclosure: I work at a company building an open source email client (https://nylas.com/N1) and an API to simplify email (https://nylas.com/docs)
Little question: do you plan to support PGP?
Microsoft didn't just turn into the biggest BASIC software company.
The point is that the outcome can often be unrecognizable from the origin, and not to worry to much about the endpoint, but focus on doing one thing well at the start.
At one job, it was like writing letters to fellow warriors across continents. You'd try to be thoughtful, taking a day or more to write really concrete and informational pieces. At another job it was basically the office instant messenger, replies were expected within 10 minutes of almost all email. Having direct reports changes a lot of how you're communicated with as well.
Right now I've been using notmuch+org-mode (to do list management that can link to emails, files, websites, etc), and so now I file tasks called "Read X" if it doesn't need immediate response, or archive/mark as read if I don't need to read it. Things that take less than a few minutes I do right away.
Once you take things as merely inputs to your personal management system, you no longer have to worry about how an app pushes it's workflow on you, you have an external one. This is why text files/physical papers are amazing - it's the lack of an interface that lets you organize things in whatever fashion makes sense.
It's nice as one more way of figuring out what to prioritise.
My inbox is often more of a conversation that I fade in and out of. Sometimes it resembles a facebook feed. Granted, I'm not a type A personality, but not all email is has to be "done" anymore than all reading books need to be "done". They can be continuous reference or contemplation for a time.
I guess it depends on if we are talking about work email or personal email. Perhaps even more, it's just about perception.