For example, right now you can only choose one tag. When you choose a
different tag, the previous one is replaced. Very simple, but limiting.
A multi-tagging universe changes this expectation: adding a new tag
doesn't remove the previous tag. More powerful, but now changing a tag
becomes a two-step operation (with the implication that there's some new
"remove this specific tag" feature).
Additionally, multi-tagging complicates the export process (what happens
if you tag an expense with two jobs -- I think QuickBooks only support
one job per expense) and so on.
Both models make sense, but it's not totally clear to me which satisfies
the most users. That said, the more requests we get like yours, the
more it tips the balance in favor of adding multi-tagging!
Thanks again. This is incredibly helpful.
-david
You are assuming tags field into one field. Most places I've been, there is a desire to have multiple "tags" - each which corresponds to a different field in the accounting system.
For example, in most accounting systems, department ("class" in QB) and "job" are different fields. More complicated systems will have even more "tags".
From a product perspective, would recommend going with 3 - that handles the common scenarios of department and job - and still have expansion for one additional tag - eg. for product line, sales program, internal tracking vs billable external job, etc.
To manage real estate and simplicity, you might have a "preference" setting where the user defines how many tags are visible on their form - along with a "default" value" for the tag.
Let me know if you would like to discuss further.
- k
--- On Wed, 12/9/09, David Barrett <dbar...@expensify.com> wrote: |
Frankly, this is a direction we've always wanted to go, but have been
putting off. Maybe we'll just need to bite the bullet and do it.
-david
Ken Jowe wrote:
> You are assuming tags field into one field. Most places I've been,
> there is a desire to have multiple "tags" - each which corresponds to a
> different field in the accounting system.
> For example, in most accounting systems, department ("class" in QB) and
> "job" are different fields. More complicated systems will have even
> more "tags".
>
> From a product perspective, would recommend going with 3 - that handles
> the common scenarios of department and job - and still have expansion
> for one additional tag - eg. for product line, sales program, internal
> tracking vs billable external job, etc.
>
> To manage real estate and simplicity, you might have a "preference"
> setting where the user defines how many tags are visible on their form -
> along with a "default" value" for the tag.
>
> Let me know if you would like to discuss further.
>
> - k
>
-david