All posts by Kerika

About Kerika

Kerika is the only task management tool that's designed specially for global, remote teams.

A new Weekly Prioritization template, inspired by Jim Collins’s work

Kerika

Jim Collins, acclaimed author of Build to Last and other well-received books, wrote an interesting blog post about 10 years ago on the importance of creating a Stop Doing list.

Mr. Collins emphasized the importance of deciding not to continue doing something any longer as key to successful prioritization:

A great piece of art is composed not just of what is in the final piece, but equally important, what is not. It is the discipline to discard what does not fit — to cut out what might have already cost days or even years of effort — that distinguishes the truly exceptional artist and marks the ideal piece of work, be it a symphony, a novel, a painting, a company or, most important of all, a life.

He cited the example of Darwin Smith of Kimberly-Clark making the critical decision to sell off the company’s paper-mills, which provided the bulk of the company’s revenues and had been in existence for 100 years (!), in order to focus on the new consumer business of paper towels.

This article has inspired us to create a new task board template called “Weekly Prioritization”: it lets you organize your work in a different way from the traditional “To Do / In Progress / Done” taxonomy of Kanban, by using columns organized as:

  • Must Do: in here, put everything that absolutely must get done that week.
  • Should Do: everything that you would really like to get done, once you get all the “must do’s” done.
  • Could Do: stuff you could do, if you had any time left
  • Stop Doing: this is the really critical column — identify everything that you should stop doing!

Let us know how useful this proves to you! (Hat tip to Eitan Nguyen for the suggestion…)

And, as usual, we will continue building new process templates to help our disparate users with their projects.

Coming up: a simpler pricing for Kerika

Kerika

We are moving to a simpler pricing scheme for Kerika:

  • As before, you can start with a free Standard Account, which will let you have two other people work on your projects.
  • Once your team grows past that point, you can upgrade to a Professional Account, which we are offering at a simple rate of $10 per user, per month (billed annually).
  • Academic & Nonprofit users can still request free service, which will now allow for up to 10 free users per account.

Three key changes with our new pricing:

  • You won’t have to buy “packs of licenses” any more: you can buy just as many as you need.
  • The new rate is higher, but reflects the tremendous increase in functionality since our November release of task boards, Kanban boards and Scrum boards.
  • The refund policy is simpler: instead of changing the subscription end-date, you will simply get a refund for the unused portion of any Professional subscription that you had purchased.

Our new pricing will continue to be very competitive, with tremendous value for your money because:

  • There are no limits on the number of projects you can create within an account.
  • There are no limits on the number of cards that you add to a particular project board.
  • There are no limits on the files that you share as part of a card (the size of your Google Drive is entirely between you and Google.)

All of our competitors are offering very complicated pricing schemes that limit your freedom to create and reconfigure projects as needed. But not us.

And, as before, we will continue to use Google Checkout for our billing, which means we will never see or store your credit card information.

Improved integration with Google Drive, faster performance, and full iPad support

Usability

Along with our best wishes for this holiday season, we have a small present to put under the tree as well: a new version of Kerika will be available on Christmas Day! This new version will come with:

  • Improved integration with Google Drive: now, you will be able share any kind of files, including music, videos, Flash, and other binary data, simply by adding them to your project cards or canvases. (When you log into Kerika again, you will be asked to reauthorize Kerika’s access to your Google Apps,)
  • Improved performance: projects should load at least twice as fast as they did before, making it a lot easier to use Kerika in coffee shops and other places with unreliable WiFi.
  • Full, fun iPad support: you will be able to access your Kerika projects using the Safari or Chrome browser on your tablet (no need to download any apps).
  • Better support for visitors: you can give project stakeholders (like your clients, for example) read-only access to your projects. They will be able to view everything in your projects except for your chat, which will remain private to the team members.

There are also usability tweaks:

  • Attachments can now be opened with a single click.
  • The “Move” action can now be found in the menu at the top of the columns.

What we are working on next:

  • A consolidated view of all your projects, similar in concept to the “unified inbox” you find on your smartphone.
  • Easier ways to manage your account, and integration with the Google Apps Marketplace and the Chrome Web Store.
  • Work estimation, work logging, and exporting of project data.

Thanks again for all your support: the very encouraging feedback we have been getting from our users continues to fuel our efforts!

Giving real thanks, this Thanksgiving

Kerika, Technology, Usability

This Thanksgiving holiday, we have good cause to be grateful to all the folks who gave us detailed feedback on our new task management software, and helped us identify about 25 different improvements that we plan to make over the next week covering areas such as:

  • Eliminating any confusion that might exist regarding project privacy;
  • Making it easier to edit card titles;
  • Making it easier to chat on individual cards;
  • Improving the emails that are sent when people are added or removed from projects;
  • Improving the overall performance, by at least by 50%;
  • Simplifying the experience for new users;
  • Simplifying the use of canvases and whiteboards;
  • Adding helpful hints throughout the product; and
  • Eliminating references to “Kanban” which some people find confusing (without eliminating any functionality).

We will be updating Kerika next week, and will continue to release new versions every two weeks, and over the next month we plan to market and publicize the software more.

Kerika isn’t written in Indonesian. (And Google Docs isn’t in Vietnamese either…)

Ephemera, Technology, Usability

An odd problem that we cannot quite figure out: every once in a while Google’s Chrome browser will tell the user that the application is written in Indonesian, and then offer to do a translation.

We cannot figure out what’s going on with this: all of the code is written in Javascript and Scalable Vector Graphics (SVG), so why would Chrome consider it to be an Indonesian page?

The problem must lie with Google Chrome itself: now, we are noticing that it will sometimes report that Google Docs is written in Vietnamese, as this screenshot shows!

Our latest version: better integration with Google, and more UI coolness

Kerika, Technology, Usability

You will have a new version of Kerika tomorrow, with a bunch of great new features. One big improvement is in Kerika’s integration with Google: we are upgrading to Google’s newer, better authentication system, so you will be asked to sign-in through Google again as if you were a brand new user — but don’t worry, none of your old projects or data are affected in any way by this change! The new sign-in process consolidates in one place all the permissions that Kerika requests with respect to your Google account; they include:

  • Access to your basic information: name, email address and photograph, which we use to make sure your Kerika account is set up properly. Now, the photo you use on Google will be used automatically for your Kerika projects as well.
  • Access to your Google Docs account, which, as before, we use to store the files you upload to your Kerika projects. Now, when you upload files to a Kerika project, they will be stored in the Google Docs account of the Account Owner. This makes it easier for Account Owners to manage all the content assets related to their projects.
  • Access to your contacts: this will be used in our next release (look for it in a couple of weeks) which will have auto-completion of names and email addresses when you invite people to join your projects.

There’s a long list of benefits that come with the new version of Kerika:

  1. When you add a URL to a Kerika page, that web site will show up as an embedded page within your Kerika page (i.e. as an IFRAME): you can customize the size and the display, so that only the content you are interested in is shown. Which means that Kerika lets you literally cut-and-paste the Internet.
  2. When you add Web content to Kerika pages, the system automatically gets the title of the Web content, so you don’t have to enter that by hand. And, of course, you can always rename it if you like.
  3. When you upload files to Kerika projects, they will now be stored in sub-folders within your Google Docs that are named for the Kerika projects. This means your Google Docs account doesn’t get cluttered with files in the same way as it did before.
  4. If you use Google Drive, you will find that your Kerika documents are available across all your computers. Kerika is well integrated with Google Drive.
  5. When someone joins a project that already has a bunch of Google Docs, they won’t get a bunch of emails any more from Google letting them know that they have access to each of these files. (These emails were kind of annoying ;-)
  6. If someone is removed from a project team, they will no longer have access to the Google Docs that were part of that project.
  7. On Firefox, Chrome and Safari (but not IE9), you will see thumbnails of the documents on your Kerika projects, which makes it easier for you to quickly distinguish between several files.
  8. When you make a project open to the public, its documents are available only to people who know the URL of the documents. We feel this is a better approach to privacy when you considering making a project open to the public.
  9. When you are uploading a large file to your Kerika project, you don’t have to wait for the uploading to finish in order to do other work inside Kerika.
  10. When you copy a project, or use someone’s public project as a template, you will get your own copies of all the documents in that project.
  11. Switching between different Kerika pages is now much faster since images are now retrieved from your browser cache instead of from the server.
  12. A long-awaited bug fix: when you have images (pictures) on your Kerika pages, they will be shown properly on Internet Explorer 9 and Safari. (We had to fix a problem with the way these browsers dealt with Google Docs.)
  13. Text blocks can now have a border color as well.
  14. The emails sent when you invite people have been improved.
  15. And, finally, the thumbnails of Kerika pages — which you can post to Facebook, LinkedIn, Google+, etc. — are much improved.

Thanks for your continued support of Kerika, and for providing feedback on how we can improve the product. There’s more good stuff coming your way, so keep collaborating…

A simpler way to deal with thumbnails

Technology, Usability

Sometimes you have to admit that your bright ideas just didn’t turn out as well as you liked…

One such bright idea was to have Idea Pages show thumbnails of their contents when viewed from their parent pages. Here’s an example of this works in practice:

Old thumbnails implementation
How thumbnails of Idea Pages used to look

A great idea in theory; not so great in practice…

The original goal was two-fold:

  1. To let users know quickly which items on an Idea Page contained other pages;
  2. To give users a quick visual sense for what was contained in those pages;

In practice, however, the effect of these thumbnails showing through all the time was a splotchy, rather ugly effect. To remedy this, we are adopting a new mechanism that we hope will continue to meet our two goals: with our latest version, any item on an Idea Page that contains another page will appear with it’s text/label underlined, like this:

What thumbnails look like now
What thumbnails look like now

As you can see, items that contain pages now appear with their text labels underlined. If you move your mouse over a shape that has underlined text in its label, you see a thumbnail appear as before:

A thumbnail appears on mouseover
A thumbnail appears on mouseover

Selecting the shape now provides a green “+” button: this lets you open the page contained within that shape.

Thumbnail on selection
Thumbnail on selection

This new green “+” button also appears on shapes that don’t contain any pages within them: in that case, clicking on the “+” button lets you create a new page that is contained within that shape.

In effect, the old double-click mouse operation has been replaced with a green “+” button that appears when you select a shape with a single mouse click.

We hope you find these changes helpful; we earnestly seek your feedback!

The value of trademarks (and other intellectual property)

Intellectual Property, Kerika

Not many startups seem to think that having a registered trademark, or a patent for that matter, can help real, tangible assets for the company. Most entrepreneurs seem to think that getting a “.com” domain name is all that’s needed to create their company’s identity.

While getting a “.com” domain name for your new company is undoubtedly valuable – and we don’t believe a “.net” or “.biz” or any other variant is nearly as worthwhile – getting a registered trademark, a registered service mark (if appropriate), and patents are all very important for startups.

Early on we registered “Kerika” and our distinctive flower logo as registered trademarks and registered service marks. Getting the registered status for a trademark is more expensive – although not prohibitively so, in our opinion – and certainly more time-consuming than simply slapping on a “TM” after your product or company name, but there are very valuable benefits from having the registration.

One simple benefit is that you can claim your registered trademark on social media platforms even if you weren’t the first to register that particular name. For example, we weren’t the first to register “kerika” as a username on Facebook or Twitter or YouTube, but we were able to get these usernames assigned to us because the word is a registered trademark, and that’s a very powerful lever to use with third-party companies.

There are other benefits, of course, particularly if your company or product name is a “made-up name” – which, incidentally, makes it a lot easier to get registered as a trademark or service mark – such as making sure that your competitors don’t try to get cute by using similar names. (Remember Jobster?)

And once you get a registered trademark, you need to remember to file additional paperwork after the first 5 years, and that’s what we finished doing recently. The US Patent & Trademark Office have improved their processes in recent years, so that when you file for an extension after 5 years of using a registered mark, you can apply for a “declaration of incontestability”, which gives you even greater rights to your product or company name.

(We just received our “declaration of incontestability” for registered trademark and our registered service mark.)

There’s a lot of value in getting a patent as well, although the cost of this can be very significant. If you have been truly innovative, and have really invented something new, you should get it patented. A patent reflects the hard work you put into your innovation: it isn’t granted lightly by the US Patent Office – despite what you may read in the press about “thousands of junk patents” being issued everyday. In our case, getting a patent for visual templates took years of waiting, hundreds of hours of effort, and cost a bundle.

But, we feel it was well worth the time and effort! If a competitor tries to copy Kerika, we will make our displeasure known!

Kerika’s blocks of richly formatted text: an example of “glass box documents”

Kerika, Technology, Usability

Our next release will primarily focused around the text block feature, which is turning out to be perhaps the single most popular feature of Kerika.

When we first built Kerika, the ability to put formatted text on Idea Pages was viewed as an incidental feature: we figured that people would want to draw flowcharts, and in doing so they would need to put small bits of text on the canvas to use as labels and markers. Nothing more.

So, we considered a variety of open-source programs that provided HTML editing capabilities for our initial versions of Kerika , before settling on Whyzziwig which appeared to have more functionality than we thought we would ever need…

However, as we started using Kerika ourselves, and talked extensively to our helpful users, we slowly realized that text blocks were a very helpful feature indeed: perhaps the most important feature in Kerika’s bag of tricks.

We have dubbed this the “glassbox documents” phenomenon: if you are sharing user requirements or collaborating on a design, you don’t need the full capabilities that come with Microsoft Word or Google Docs. Instead, what you really need is the ability to quickly write relatively small bits of text, perhaps a few paragraphs long, with a table or some links and pictures, and use these to mark up an Idea Page.

Here’s an example of how we used these text blocks for developing the next version of Kerika, which will contain a hugely improved text block feature:

Example of using Kerika to design a user interface
Example of using Kerika to design a user interface

 

This picture shows an Idea Page that we used to share ideas between the designers, users and developers about how the text block feature could be improved.

  • In the middle of the Idea Page, we have a mockup of a new text block toolbar, to replace the existing Whyzziwig toolbar.
  • Above it are various pages that define the working of each button: inside each of these sub-pages we have small blocks of text that provide the detailed requirements for a particular button, as well as design notes from the developers and test data from the QA team.
  • Towards the bottom you can see a larger text block contain additional notes about the design.

Using text blocks in this manner, to capture and share our ideas and designs, we have reached that ultimate state of perfect collaboration: even though the Kerika team is distributed between Bellevue and Issaquah in Washington State, and Gujarat and New Delhi in India, we have zero emails being sent within the team!

This is the power of a glassbox document: the ability to sharply increase productivity and shared understanding of requirements and design, by putting text directly on an Idea Page instead of hiding it inside a conventional document (which we would call a “blackbox document”).

Playing whack-a-mole with Google Docs and Chrome: where’s your image being stored today?

Technology

We recently talked about a shift within Google Docs that resulted in their using a new domain name – googleusercontent.com – to store images that users upload.

The way Google stores images on various sub-domains of googleusercontent.com is a bit of a mystery to us: it isn’t just that when you upload images to your Kerika pages they get stored by Google in some seemingly-random sub-domain of googleusercontent.com, but that the location may change from day to day!

This is making it very hard to run the Chrome browser with the “Disable third-party cookies” preference turned on, because you may find that each day some of the images on your Kerika pages are not being displayed because they have suddenly shifted to a different sub-domain of googleusercontent.com – one that you haven’t previously whitelisted.

Firefox used to have a very simple way of whitelisting domains for which you were happy to get cookies, but that disappeared several versions.

Chrome doesn’t offer any easy way of whitelisting domains either, presumably because Google is strongly in favor of third-party cookies since these underpin so much advertising. There’s an extension for Chrome called “Vanilla Cookies” that supposed to allow you to whitelist domains using wildcards, but it doesn’t seem to solve the whack-a-mole problem with googleusercontent.com as far as we can tell.

Now, your only options appear to be:

  • Disable all third-party cookies, which means that images you upload to your Kerika pages are not shown because they are being stored somewhere on googleusercontent.com, which is a third-party since it is neither kerika.com nor google.com, or
  • Allow all third-party cookies which means all sorts of junk can find its way onto your computer.