4 ms·

> Even we cannot see your decision contents. How? I read through few other pages and don't see this described. On "How It Works"[0], everything after the firs

> Even we cannot see your decision contents. How? I read through few other pages and don't see this described. On "How It Works"[0], everything after the first "step 3" seems mostly worthless for every team I've ever worked on and feels like it's more like something that isn't for me? Like who gets something out of those when it's a product (that heavily pushes their slack integration) for "teams" to record decisions? [0] https://loqbooq.app/how-it-works https://loqbooq.app/how-it-works

tonyjstark 5y ago
Thanks for the feedback! > How? I read through few other pages and don't see this described. We encrypt the important fields in the DB, besides having encryption at rest. Of course, with enough effort we could see the content of decisions, but we would need to take the additional effort. We try to separate us as much as possible from our users data. Maybe we should clarify that on the home page. on your second point: I think we still have to tune our communication. Of course, maybe it just isn't something for you, hard to tell, depends on your existing decision taking process in your team and on the projects you work on. Can you elaborate on why it's not for you? Maybe we miss out on scenarios and could improve our app there, we don't consider it 'done'. We hope that Loqbooq can help with long running projects where (software) design decisions but also management decisions get lost over time. We also hope Loqbooq helps if problems arise between co-working parties in projects.
- bpeebles 5y ago
  > Even we cannot see your decision contents. Reads to me it's impossible for you to see them, as if you used client-side encryption of some sort. It's good to hear it's well protected as is, but I'd reword it. For the later messaging, I'm just trying to think about what situations one would be in that this would need to be immutable and verifiable in this way. Like something would have had to have gone very very wrong so having that be a big part of your sell feels vaguely blockchainy/scammy (to me). Keep it sure, but make it a smaller part of your pitch and focus on the common path of helping a long-lived team documenting and referencing decisions, which was what I was mostly looking for. Thanks for the reply!
- valenterry 5y ago
  > Of course, with enough effort we could see the content of decisions Yeah as in "if I don't look, I won't see it". Making such a claim ist just misleading people.
  - tonyjstark 5y ago
    We'll reword it, so that it's more clear what we do. We definitely don't want to mislead people. On the contrary!

tonyjstark 5y ago

Thanks for the feedback! > How? I read through few other pages and don't see this described. We encrypt the important fields in the DB, besides having encryption at rest. Of course, with enough effort we could see the content of decisions, but we would need to take the additional effort. We try to separate us as much as possible from our users data. Maybe we should clarify that on the home page. on your second point: I think we still have to tune our communication. Of course, maybe it just isn't something for you, hard to tell, depends on your existing decision taking process in your team and on the projects you work on. Can you elaborate on why it's not for you? Maybe we miss out on scenarios and could improve our app there, we don't consider it 'done'. We hope that Loqbooq can help with long running projects where (software) design decisions but also management decisions get lost over time. We also hope Loqbooq helps if problems arise between co-working parties in projects.

bpeebles 5y ago
> Even we cannot see your decision contents. Reads to me it's impossible for you to see them, as if you used client-side encryption of some sort. It's good to hear it's well protected as is, but I'd reword it. For the later messaging, I'm just trying to think about what situations one would be in that this would need to be immutable and verifiable in this way. Like something would have had to have gone very very wrong so having that be a big part of your sell feels vaguely blockchainy/scammy (to me). Keep it sure, but make it a smaller part of your pitch and focus on the common path of helping a long-lived team documenting and referencing decisions, which was what I was mostly looking for. Thanks for the reply!
valenterry 5y ago
> Of course, with enough effort we could see the content of decisions Yeah as in "if I don't look, I won't see it". Making such a claim ist just misleading people.
- tonyjstark 5y ago
  We'll reword it, so that it's more clear what we do. We definitely don't want to mislead people. On the contrary!