A new video that is the shortest summary we have ever made of Kerika:
Kerika in 70 seconds from Arun Kumar on Vimeo.
This is going to feature in our all-new website redesign, which we hope to get in place this week.
Tag Archives: Task Board
From Projects to Boards: a clarification
We used to refer to “Projects” and “Boards” somewhat interchangeably on our website, our blog and in the Kerika app itself.
There was no special reason for this: in our mind, a Project was clearly a Board, and vice-versa, and it never occurred to us that this might prove a source of confusion to anyone.
Well, we were wrong about that.
In the real world, people are very cautious about “starting a new project”, because this might involve getting formal administrative approval, budget allocation, staff changes, etc.
In other words, in the real world a “project” is a big deal.
But, in Kerika, starting a new Task Board, Scrum Board or Whiteboard is not a big deal — and that is very much by design.
Unlike so many other collaboration tools that make it difficult for you to create as many boards as you like, Kerika was always designed to make it very easy for you to redesign your work as needed: start new boards, move cards or canvases from one board to another (using Cut, Copy and Paste), and to move ideas and content from one context to another.
Many of our competitors don’t offer this kind of flexibility: either the software makes it hard, or their billing model actively discourages you from creating multiple boards.
That will never be the case with Kerika: we will always support flexibility in how you organize and manage your boards.
Still, our interchangeable use of “projects” and “boards” was definitely causing some confusion, which we have fixed with our latest release by using the term “Board” consistently and avoiding use of the term “Project”.
So, if you were a Project Leader previously, you are now a Board Admin on that board. Your rights and privileges remain the same, it’s just your title that changed.
When you start a new board, what used to be called “New Project” is now labeled “New Board” to make it clear what you are doing:
We hope this makes for better usability: let us know what you think.
How you can tell if your Project Team has changed
If you are the only Project Leader on a Task Board, Scrum Board or Whiteboard, you will know when someone joins a board — after all, you would have approved their invitation in the first place.
But, if there are several Project Leaders for a board, it might be one of the others who added somebody to your board, and they might not have discussed this with you…
So, Kerika makes sure you know whenever the project team on any board has changed in any way:
- If someone has joined,
- If someone’s role has changed,
- If someone has left.
(After all, someone could have left the team on their own, without telling you!)
Whenever there is a change in the project team, the Board Settings button on the top-right of the board will appear in orange.
Click on the Board Settings button, and you will see the Team tab is highlighted: this is Kerika’s way of drawing your attention to this particular tab within the Board Settings display.
When you go over to the Team tab, you will see that the new person’s name is highlighted in orange, for a few seconds. It’s a discrete yet very effective notification from Kerika, drawing your attention to the presence of someone new on the team.
The same kind of notification is used when someone’s role on the team is changed, e.g. from Team Member to Visitor.
Kerika also tries to let you know when someone has left the team, by highlighting the Project Settings button in orange, and the Team tab within the Project Settings in orange as well.
Smart notifications, from Kerika — the only work management system that’s designed specially for distributed Lean and Agile teams :-)
Attaching content to the board itself, not just to cards
We have added a new feature that should prove handy for a lot of folks: you can now add content — files from your laptop, images from your mobile or tablet, Web links from your Intranet or the Internet, or canvases — to a Task Board or Scrum Board itself.
If this sounds like something that was always there, maybe we need to say that differently: you used to have the ability to add content to a card, now you can add it to the board itself.
There are many situations we have encountered where we want to share content or a canvas with a team, but there wasn’t any obvious place to still it — no single card on the board that seemed like the right place to attach that content.
And that’s because the content we wanted to add was applicable across the entire board, not just relevant to a single card.
This was getting frustrating, so we decided to scratch our itch: a new button on the top-right area of your Kerika app will let you add files, Web links and canvases to the board itself:
This should make some of you as happy as it has made us!
Adding a Google Map to your Kerika canvas
Did you know that you can embed a Google Map in your Kerika Whiteboards? It’s easy: just copy the Google Map’s URL:
And paste it into the dialog box that appears when you click on the “Add Web Content” button on your canvas toolbar:
Kerika automatically figures out the URL refers to a Google Map, and shows you an embedded map on your canvas:
You can do the same thing with card attachments, for your Task Boards and Scrum Boards: Kerika shows a small thumbnail of the map in the list of attachments on your card:
UI tweak: showing attachments in chronological order
It used to be that when you added content to a card — files from your laptop or Web content from your Intranet or the Internet, or a canvas — the newest content was added at the top of the list.
Of course, you could always rearrange them, by grabbing and dragging them up or down the list, but this it not a feature that many users discovered on their own :-(
Well, for greater consistency with how the chat and history are shown within a card’s details, we are now going to show attachments in chronological order as well — the latest files and URLs that you added to a card will appear at the bottom of the list, and the view of these will be automatically scrolled to show the latest items:
An easy way of keeping track of sub-tasks
With our latest update, it’s become easy to keep track of sub-tasks for cards on a Task Board or Scrum Board; here’s an example:
In the example shown above, the second item in the numbered list has been been taken care of, and so it has been struck-through, making it clear to the rest of the team that it isn’t an issue any more.
We have added the capability of marking text within card details with a strike-through, and this, combined with the easy way in which you can create numbered lists, makes it easy to track sub-tasks!
UI tweaks: new icons to allow for a future feature
At the time we added “In Progress” as a new status value, we also removed the “Done” status, mostly because the drop-down list of status choices was becoming rather long — and “Done” was not quite like all the other choices that we were presenting for marking a card’s status.
This is what the old choices looked like:
And this is what the new status choices look like:
There are two small UI tweaks here that we made:
- A purple color is now used for “Needs review” — this previously was green, but green was really the best choice for “In Progress”, and we didn’t want to use the same color for two different states.
- The icon for “Critical” has been changed to look like a fire: that’s because we want to reuse the old triangle icon in the future for a great new feature that we are still brainstorming — a way to mark certain cards as “troubled”.
UI tweaks: avoiding errors in the right-click menu
Building a great user experience is rarely the result of big, bold actions: more often it is the cumulative gain of a large number of very small tweaks we make to our user interface design.
Here’s an example: the right-click menu, when you click on a card on a Task Board or Scrum Board, used to look like this…
This menu is a little crowded, and one irritating source of errors was that people would sometimes click on one of the Move choices (Move to Done, Move to Trash or Move to Backlog) when they intended to do click on one of the others choices instead.
The irritation came from the fact that these Move operations had a much bigger impact than the others: for example, if you accidentally cut a card, you can reverse that operation by selecting the cut cards once more, which would effectively “undo” the cut.
But, if you move a card to Trash or Backlog, it was a lot more hassle to get it back: you had to make sure the Trash or Backlog was currently being displayed — and in many large boards these columns are routinely hidden from view by the user — and then find and drag that card back to where it was.
So, here’s our small UI tweak to reduce the chances of this error:
A simple visual cue, in the form of grey horizontal separator lines, helps remind the user that some of these right-click mouse operations are “more significant” than others, by creating a visual segregation of these options from others.
A simple UI tweak that helps reduce errors by our users, and one that adds up to a great user experience!
An improvement to Card History
Every card, on every Kerika Task Board or Scrum Board, contains within it a full history: a log of all the changes that have been made to it.
(A few actions are ignored because they can occur so often, and are often inconsequential, e.g. moving a card up/down within the same column. In contrast, moving a card across columns is considered consequential, and is therefore logged in the card history.)
We recently made a usability improvement in the way the Card History appears: the log of changes is now shown in chronological order, rather than reverse chronological as was the case before.
This makes history look more like chat, and should make it more usable!