Group items tagged

Evernote Hello is based around the three fundamental ways that our brains actually remember people: Faces: What do you look like? Time: When did we meet? Context: Why did we meet and who else was there? That’s all there is to it. Whether you’re at a big conference, catching up with people at a coffee shop or joining a meeting in your office conference room, these concepts hold true. Here’s how it comes together.

Related notes from Evernote This is where things get really interesting. Evernote Hello will automatically display notes made in Evernote or Evernote Food around the same time as your encounter. Say you met someone at a conference (Evernote Hello) and had lunch with them (Evernote Food), all the while taking notes on your laptop (Evernote). The app will show you everything when you view this person in Evernote Hello—even more context.

Encounters As soon as you add an individual to Evernote Hello, the app automatically creates an Encounter with this person. An Encounter consists of the person’s profile, the location of your meeting and any additional information you’d like to add that will make the event more meaningful for you later. The app lets you attach photos and notes to your encounters.

One of the themes that came up a lot was the idea of the growth team finding a leading indicator of a user who would turn into an engaged user later on. The growth team would then focus on optimizing for that metric. 

Characteristics of leading indicator metrics The various leading indicators fit into three categories: Network density: friend or following connections made in a time frame Content added: files added to a Dropbox folder Visit frequency: D1 retention

Other points from the speakers A few other interesting things were mentioned at the conference. Josh Elman mentioned that Twitter has two degrees of an active user: a plain “active user” is someone who has visited their timeline at least once in the last 28 days a ‘retained’ or ‘core’ user is someone who has visited their timeline at least 7 times in 28 days.

The best will be in contact all the time (or at least well before they have a news story to pitch) in an attempt to figure out how to maximize the chances of something being picked up. It’s a wonder there aren’t more of them.

Sadly there aren’t and 80 - 90 percent of pitches I received followed the tired format of "Hi X, Company Y is launching a product next week and we thought it would be of interest to publication Z."

So here's an idea to try when getting media coverage for your startup - don't start by pitching the product. Start by pitching nothing.Clearly showing that you understand that a journalist doesn't just exist to publicize you is one of the fastest routes to his or her heart.

The question The main question in play here is: How thick should clients be? Let me define my terms: I define the Client as the thing which is used by exactly one user, which interacts directly with that user, and which is probably physically close to that person. I define the Server as the thing which is shared by multiple users, which interacts directly with the Client, and which could be physically located anywhere. I define the Pipe as the connection between the Client and the Server. I define the notion of a Thick client as a relative term. Thicker clients have more app-specific code and are less dependent on the Server. Thinner clients leave more of the app-specific work to be done on the Server. There are two main variables in decisions about the thickness of clients: The quality of the Pipe: This includes bandwidth, latency, availability, reliability, and cost The Client side costs: This includes cost of hardware, software development, deployment, upgrades, and maintenance. And, there are two laws which apply: As the quality of the pipe goes up, the client can get thinner. As the client side costs go down, the client can get thicker.

This issue is not new Back in the 1960s and 1970s, when we only had mainframes and minicomputers, there was a distinction between smart terminals (thick clients) and dumb terminals (thin clients). In the 1980s, we got workstations (really expensive thick clients, purchased by people who perceived them as cheap compared to the mainframes and minis) and microcomputers (far less expensive thick clients, purchased by people who previously didn't have a computer at all). In the early 1990s, the high cost of workstations gave rise to X terminals, thin client devices which couldn't do much more than display the graphical user interface. My manager bought one of those fancy new 19.2k modems and actually tried doing Motif widget development from home. In the mid 1990s, web browsers appeared. For a very brief time, this technology was regarded only as a way to collaborate on hypertext documents. This phase of the web lasted for most of an afternoon. Meanwhile, back in Champaign, Illinois, the Unsung Hero and His Eminence were busy building a web browser which had more "stuff" in it. What kind of stuff? The sort of stuff that made web browsers into a platform for delivery of apps. And the technologies of the web have been moving primarily in that direction ever since. Java applets (developed a fatal disease called Swing) ActiveX (declared dead seven years after it went missing) Flash (murdered by Steve Jobs) Silverlight (murdered by HTML5) In the late 1990s, people (Oracle, I think?) tried to sell something called a Network Computer. It was a little PC with a video card, some RAM, an ethernet card, a web browser, and no hard disk. Thin.

HTML5 arrived. Actually, the spec is still a long way from being finalized, but nobody knows that. People needed a name, so they started saying "HTML5" before it was fully cooked. Common usage of the term "HTML5" is actually fairly accurate, at least compared to the way telecom companies use the term "4G". And now, this war has moved to the battlefield of mobile. Smartphones and tablets.

We’ve listed some best practices to help marketers stay compliant with Canada’s new anti-spam law: Be very clear on who is sending the message. A marketer sending a message on behalf of a brand could be responsible. Follow the subscribers rule – get permission (explicit permission) to email your subscribers. If there’s not a request for consent, it’s not consent. Respect and govern the one-to-one marketing relationship that you have with subscribers. Honor each individual’s unique preferences with regard to communication, content, frequency and channel. Provide recipients with an obvious, clear and efficient email or web-based means to opt-out of receiving any further business and/or marketing email messages from your organization. Keep records of the type of consent obtained from recipients so that email lists can be scrubbed prior to campaign broadcasts. Include a link to your company’s privacy policy in every email. The privacy policy should explain the intended use and disclosure of any personal information that might be gathered through “clickstream” means or other website monitoring techniques. Take reasonable steps to ensure that the addresses on your email lists were obtained with proper consent.

For more information on the legislation, visit the Government of Canada’s Anti-Spam Legislation website at: www.fightspam.gc.ca.

Regardless of the law, explicit permission is the best practice and produces the top results and deliverability.