Simplton Town Ordinances

  • No priority levels.
  • No page refreshes (almost).
  • No lame search implementation.
  • No limits to email.
  • No issue titles or subjects.
  • No milestones.
  • No dashboards.
  • No "assigned to" feature.
  • No tag soup.
  • No projects.
  • No user taxes.
  • No startup businesses taxes.

No priority levels

The problem with priority levels is that almost 99.9% of issues are a "high" or "critical" priority (or so the submitter likes to think). Simplton does away with the "low","medium","high", and "critical" priority mind set. A more natural idea of issues bubbling up or down is how things are down 'round here. After 15 days, if a bubbled up issue has no activity, it is automatically bubbled down. This way the top of your list is filled with issues that are truly a priority.

No page refreshes (almost)

Keeping page refreshes to a minimum equals a responsive user interface. You do not go to separate page to view the issue history, revise an issue, or to make a new issue. All of these interactions and more are made "inline", without leaving the page. Think of Simplton as the issue tracker equivalent to Gmail. Please check out the short screencast on this matter.

Search is so vital; however, for many bug and issue trackers it is a slapped in feature thats usefulness is a low (or bubbled down) priority. Simplton always has great search in mind and there have been many hours spent making search outstanding. There are a wide range of ways to narrow down and find the issue you are looking for. If search is not great your tool will fail to gain team adoption. Why? The bug and issue tracker doubles as a knowledge base and finding past issues is crucial. If you can't search well and fast your team will go back to email where search is implemented very well.

The problem with priority levels is that almost 99.9% of issues are a "high" or "critical" priority (or so the submitter likes to think).

No limits to email

Email is not going away anytime soon, therefore, Simplton works richly with email. If you are going to wean the team off of email you must integrate with it seamlessly. There is support for revising and making new issues all via email. You can close and open issues through email. You may email anybody you want, within the team or externally, when revising or creating a issue. You may even send emails in a stand-alone fashion to anyone you want. Through email, you may remind a team member that an issue is waiting for their answer.

No issue titles or subject line

Simplton has no title or subject field for new issue submissions. The subject field is a friction point because you have to think about summarizing the new issue. Then the submitter usually repeats themselves in the issue description. Simplton automatically creates issue titles of the original issue by compacting the first 100 words of the description.

No milestones

Look, everything had to be done two weeks ago. Based on this truth milestones become millstones (around the neck that is). Again, priority is managed by bubbling an issue up and keeping them near the top of the list. Does anyone pay attention to those milestone progress bars? Does that mean you are done once the milestone progress bar is at 100%?

The subject field is a friction point because you have to think about summarizing ...

No dashboards

Dashboards just get in the way. Applications like email,instant messaging, and word processing do not have dashboards. Yet many bug and issue trackers get in your way with dashboards. Simplton makes use of browser tabs and different color favicons so you can quickly access the list you want and then get back to what you were previously doing. Each list has a comprehensive history log detailing actions like bubbling, tagging, revising, and many other actions. The history log gives a detailed snapshot of list activity quickly, without being bothered by some dashboard.

No "assigned to" field

Instead a more lightweight idea of group members declaring what they are working on. Assigned fields don't jive well with small teams whose members are trusted. Members in the small teams should be confided in to assign themselves issues to work on (ideally ones that are bubbled up). Simplton was not designed for a use cases in where one member is assigning other members things to do.

No rich text editing

When users have to decide to make something bold, or highlighted, or which font size and color to use that adds weight with very little benefit. If you want some text to get attention, make it all caps. What is supported is a range of auto linking support. For example anything that matches "http://[url]" or "issue [issue number]" or "attachment [attachment number]" or "post [post number]" will be auto linked.

...milestones become millstones (around the neck that is)

No tag soup

Tagging normally gets abused and commonly leads toward the state of "tag soup". Tag soup is when there are so many tags for an issue defined that they are no longer useful. Simplton tries to prevent tag soup from occurring by making it somewhat difficult to define them in the first place. Tags cannot be created on new or revised issues. Similar to the exclusion of the subject field, getting rid of the tags field on revisions and new issues aids in the aim of reducing friction. There is sort of a weight added when the tag field is staring you in the face, like you feel bad or lazy for not assigning a tag to the issue.

No projects

The working area instead is described as a list. List denotes how humans naturally like to organize. Simplton goes to great lengths in making working with many different lists at the same time pleasurable. For example, even favicon's for each list are a different color.

Simplton was not designed for use cases in where one member is assigning other members things to do.

No user taxes

Simplton is completely free right now but even when it goes pay there will never be a per user charge. The whole point of a collaboration tool is to get a group of people communicating in one spot. Adding users should be free and encouraged. This town will never have a "user" tax.

No startup business taxes

Startup businesses will always be free for the first two years of using Simplton. "Startups" are trying to change the world but they need time to do so. These types of business are invited to come and set up shop in our startup friendly town.

Simplton is built from the ground up to keep your team off of email as their exclusive means of collaboration. What is it worth to your business to have your team in one primary place for collaboration? Come to our town.

What is Simplton? Let's start with what it is not.

 
 
Terms & PrivacyCopyright ©