# Session overview

This is the output of our **workshop/ideation session around Open Points** on Friday (3 May 2024). This is also a test of a newer, more structured way of designing a feature by following a UX-led approach.

**Present:**

* <mention class="mention" data-id="42086" data-type="user" data-text="@Wieland Lindenthal">@Wieland Lindenthal</mention>&nbsp;

* <mention class="mention" data-id="72513" data-type="user" data-text="@Parimal Satyal">@Parimal Satyal</mention>

* <mention class="mention" data-id="72512" data-type="user" data-text="@Marc Alcobé">@Marc Alcobé</mention>


#### We worked on identifying:

* Perceived problems

* Benefits and added value

* Feature ideas

* Usage scenarios


#### **Next steps:**

Next: core feature team will work through the produced material in this document, including ones added by others after the session. This will involve:

* Rewriting and consolidating scenarios (if necessary)

* Identify those benefits, problems and scenarios that we want Open Points to address

* Introduce constraints (time, effort, money, resources, tech stack)

* Work on specification + visuals based on the above


# Raw output

## **Perceived problems**

Begin of the insertion<figure class="table op-uc-figure_align-center op-uc-figure"><table class="op-uc-table"><thead class="op-uc-table--head"><tr class="op-uc-table--row"><th class="op-uc-table--cell op-uc-table--cell_head"><p class="op-uc-p"><strong>Item</strong></p></th><th class="op-uc-table--cell op-uc-table--cell_head"><p class="op-uc-p"><strong>Remarks</strong></p></th></tr></thead><tbody><tr class="op-uc-table--row"><td class="op-uc-table--cell"><p class="op-uc-p"><strong>IntimidatingEnd of the insertion Begin of the deletion * **IntimidatingEnd of the deletion large Begin of the insertionscope</strong>:End of the insertion Begin of the deletion scope:**End of the deletion When I see specs, I get stressed because the topic is too large. Hard for me to give a simple answer; need to first create a (mental) envelope to give it space. Need to think larger to give even a smaller Begin of the insertionanswer.</p></td><td class="op-uc-table--cell"><p class="op-uc-p">YES. Breaking down larger questions (already identified as needing clarification) into manageable chunks is a useful problem to solve. Especially if there is sub-categorisation.</p></td></tr><tr class="op-uc-table--row"><td class="op-uc-table--cell"><p class="op-uc-p"><strong>WhenEnd of the insertion Begin of the deletion answer.

* End of the deletion I Begin of the insertioncomment, I want the context of the commentEnd of the insertion Begin of the deletion would like for itEnd of the deletion to be Begin of the insertionmore evident. </strong>(If it's about aEnd of the insertion Begin of the deletion easier to answerEnd of the deletion certain Begin of the insertionpart of a text that I'm responding to, I want to attach somehow that bit ofEnd of the insertion Begin of the deletion questions. To makeEnd of the deletion the Begin of the insertiontext so that the person who is looking at the question does not have to go through the whole thing).</p></td><td class="op-uc-table--cell"><p class="op-uc-p">YES. The ability to comment/mark specific bits for discussion/communication would make it easier to respond to just that bit.</p></td></tr><tr class="op-uc-table--row"><td class="op-uc-table--cell"><p class="op-uc-p"><s><strong>Cognitive load</strong>:End of the insertion Begin of the deletion problem smaller, more container.

* **Cognitive load:**End of the deletion I find it cognitively hard for short-term memory people (like managers), to be able to respond to a multi-question prompt and not miss important details. Long texts are stressful. If Begin of the insertionIEnd of the insertion Begin of the deletion \*I\*End of the deletion send four questions, I know for example that I might not get all the Begin of the insertionanswer.</s></p></td><td class="op-uc-table--cell"><p class="op-uc-p">Same as the above two: break down into smaller pieces + more context.</p></td></tr><tr class="op-uc-table--row"><td class="op-uc-table--cell"><p class="op-uc-p"><strong>LackEnd of the insertion Begin of the deletion answer.

* **LackEnd of the deletion of Begin of the insertionfocus</strong>:End of the insertion Begin of the deletion focus:**End of the deletion If there are multiple topics, I get stressed; for example, if a second topic comes up before a first one has been Begin of the insertionresolved.</p></td><td class="op-uc-table--cell"><p class="op-uc-p">YES. The ability to move forward in parallel (so that I don't feel like if I address point Nº4, that point Nº2 will be ignored). (Hint: threading?)</p></td></tr><tr class="op-uc-table--row"><td class="op-uc-table--cell"><ul class="op-uc-list"><li class="op-uc-list--item"><p class=" op-uc-p"><strong>Spread out:</strong>End of the insertion Begin of the deletion resolved.

* **Spread out:**End of the deletion Not great when information gets spread out in the application (OP); Begin of the insertionit'sEnd of the insertion Begin of the deletion it&#39;sEnd of the deletion costly to get everything Begin of the insertiontogether.</p><ul class="op-uc-list"><li class="op-uc-list--item"><p class=" op-uc-p">NeedEnd of the insertion Begin of the deletion together.

* NeedEnd of the deletion to choose Begin of the insertionproject</p></li><li class="op-uc-list--item"><p class=" op-uc-p">Choose assignee</p></li><li class="op-uc-list--item"><p class=" op-uc-p">TheEnd of the insertion Begin of the deletion project

* Choose assignee

* TheEnd of the deletion thing goes out, and nobody responds (or misses the Begin of the insertionnotification)</p></li><li class="op-uc-list--item"><p class=" op-uc-p">PrioritisingEnd of the insertion Begin of the deletion notification)

* PrioritisingEnd of the deletion becomes Begin of the insertionharder</p></li><li class="op-uc-list--item"><p class=" op-uc-p">SlowsEnd of the insertion Begin of the deletion harder

* SlowsEnd of the deletion down resolution as a result (async is great, but syncing to find resolution to everything is Begin of the insertioncomplicated)</p></li></ul></li></ul></td><td class="op-uc-table--cell"><p class="op-uc-p">YES, it would be useful to have the actual response request attached to the thing that it's related to (so that the question is not somewhere completely different). (Ease of information finding)<br><br>YES, if the people whom an open point is directed to are able to easily see them all in one place. (Ease of attention management)<br></p></td></tr><tr class="op-uc-table--row"><td class="op-uc-table--cell"><p class="op-uc-p"><strong>Too many tools: </strong>Having to rely on external tools like Element, which makes dicussion easy but finding relevant decisions later difficult.<br><strong>Async answer need: </strong>If there is a topic that is not something that can be discussed immediately in a current meeting (becaus it can take a long time and the other person might not be ready to answer it immediately), I might pick a tool that I know will go faster, like Element. But this has other problems (documentation, shared info etc).</p></td><td class="op-uc-table--cell"><p class="op-uc-p">YES, if people are able to use OpenProject for async communication too and don't need to rely on external tools like Element. (So that they can easily find this information again). The ability to document decisions and the conversations that led to it would reduce the need to rely on Element.</p></td></tr><tr class="op-uc-table--row"><td class="op-uc-table--cell"><p class="op-uc-p"><strong>UnbalancedEnd of the insertion Begin of the deletion complicated)

* **UnbalancedEnd of the deletion spread of Begin of the insertionwork</strong>:End of the insertion Begin of the deletion work:**End of the deletion Organisation vs. work is usually done by one person, others check Begin of the insertionwhat'sEnd of the insertion Begin of the deletion what&#39;sEnd of the deletion assigned for them and do Begin of the insertionwork.<br>DoesEnd of the insertion Begin of the deletion work.

* DoesEnd of the deletion not allow for collective definition of specs or topics to be Begin of the insertionaddressed.</p></td><td class="op-uc-table--cell"><p class="op-uc-p">YES, if it's possible for open points to some how have "assignees" (or be directed to someone). ThenEnd of the insertion Begin of the deletion addressed.

* **If something is not time-boxed** (andEnd of the deletion I Begin of the insertionknow thatEnd of the insertion Begin of the deletion thinkEnd of the deletion it Begin of the insertionwill not get ignored.<br><br>NO if it's related to meeting agendas and who is responsible for an agenda. YouEnd of the insertion can Begin of the insertionpossibly associate an Open point to an agenda and have someone be responsible for <i>that</i>.&nbsp;</p></td></tr><tr class="op-uc-table--row"><td class="op-uc-table--cell"><p class="op-uc-p">In the course ofEnd of the insertion Begin of the deletion takeEnd of the deletion a Begin of the insertiondiscussion (a meeting), an interesting idea comes but, but this it is not the right time to discuss it. However, if we don't address it but also don't give itEnd of the insertion Begin of the deletion long time), I might pickEnd of the deletion a Begin of the insertionclear next step, itEnd of the insertion Begin of the deletion tool that I knowEnd of the deletion will Begin of the insertionbe ignored or will be lost. There needs to be a way to mark them for someone to get back to, so that we can then continue with the normal courseEnd of the insertion Begin of the deletion go faster, like Element. But this has other problems (documentation, shared info etc).

* **LackEnd of the deletion of Begin of the insertionthe conversation or meeting.<br></p><ul class="op-uc-list"><li class="op-uc-list--item"><p class=" op-uc-p"><s><strong>Lack of structure</strong>/<strong>objective</strong>/<strong>scope</strong>:End of the insertion Begin of the deletion structure**/**objective**/**scope**:End of the deletion If we have a meeting to discuss 3 topics, some of them require more discussion than others. Without structure, we can have interesting or good ideas, but it Begin of the insertiondoesn'tEnd of the insertion Begin of the deletion doesn&#39;tEnd of the deletion move forward. There might be divergent state, but lack of convergence means that the topic remains open. For topic A, the discussion Begin of the insertionneeds:</s></p><ul class="op-uc-list"><li class="op-uc-list--item"><p class=" op-uc-p"><s>ContextEnd of the insertion Begin of the deletion needs:

* ContextEnd of the deletion (why we are talking about Begin of the insertionit)</s></p></li><li class="op-uc-list--item"><p class=" op-uc-p"><s>TheEnd of the insertion Begin of the deletion it)

* TheEnd of the deletion problem (what needs a decision or a Begin of the insertionresolution)</s></p></li><li class="op-uc-list--item"><p class=" op-uc-p"><s>PeopleEnd of the insertion Begin of the deletion resolution)

* PeopleEnd of the deletion (who needs to be Begin of the insertioninvolved)</s></p></li><li class="op-uc-list--item"><p class=" op-uc-p"><s>Action:End of the insertion Begin of the deletion involved)

* Action:End of the deletion What can be do about it (discuss it now, decide to Begin of the insertiondiscussEnd of the insertion Begin of the deletion disucssEnd of the deletion it later, create a separate Begin of the insertionmeeting)</s></p></li></ul></li></ul></td><td class="op-uc-table--cell"><p class="op-uc-p">YES if public: If I can quickly write down a "Question for Jon for later" or something to get back to myself (spin-off for later), then that does not have to interrupt the flow of an existing conversation.<br><br>NO if private: Is not meant to be a to-do list or reminder for myself (something like 'marking' or 'flagging' might be more relevant for this).</p></td></tr><tr class="op-uc-table--row"><td class="op-uc-table--cell"><p class="op-uc-p"><strong>StructuralEnd of the insertion Begin of the deletion meeting)

* **StructuralEnd of the deletion difficulty with Begin of the insertionexpression/context</strong>: Can'tEnd of the insertion Begin of the deletion expression/context:** Can&#39;tEnd of the deletion express myself properly sometimes with just text; easier if I have some visual cues, photos, sound, geolocation, measurements, Begin of the insertioncategorisation.</p></td><td class="op-uc-table--cell"><p class="op-uc-p">MAYBE: Maybe I need to be able to add more than just text to be able to express a problem or a need precisely. (Somethings like images, emojis and categories are surely a YES, something other things like sounds, maybe). But this isn't inherently something that Open points will solve, it it would be another line of exploration.</p></td></tr></tbody></table></figure>

End of the insertion Begin of the deletion categorisation.


End of the deletion ## **Benefits and added value**

How are things going to be better compared to today?

Begin of the insertion<figure class="table op-uc-figure_align-center op-uc-figure"><table class="op-uc-table"><thead class="op-uc-table--head"><tr class="op-uc-table--row"><th class="op-uc-table--cell op-uc-table--cell_head"><p class="op-uc-p"><strong>Item</strong></p></th><th class="op-uc-table--cell op-uc-table--cell_head"><p class="op-uc-p"><strong>Remarks</strong></p></th></tr></thead><tbody><tr class="op-uc-table--row"><td class="op-uc-table--cell"><p class="op-uc-p"><strong>Reduce Stress</strong>:End of the insertion Begin of the deletion * **Reduce Stress**:End of the deletion no longer need to remember stuff, not forget something, by knowing Begin of the insertionI'llEnd of the insertion Begin of the deletion I&#39;llEnd of the deletion back to it Begin of the insertionlater</p></td><td class="op-uc-table--cell"><p class="op-uc-p">YES. Especially if I can someone mark things as "done" (then it no longer needs to pay rent to live in my mind).</p></td></tr><tr class="op-uc-table--row"><td class="op-uc-table--cell"><p class="op-uc-p"><strong>ReduceEnd of the insertion Begin of the deletion later

* **ReduceEnd of the deletion mental Begin of the insertionload</strong>:End of the insertion Begin of the deletion load:**End of the deletion I can unload a thought from my head to a system; Begin of the insertionit'sEnd of the insertion Begin of the deletion it&#39;sEnd of the deletion not lost, Begin of the insertionthere'sEnd of the insertion Begin of the deletion there&#39;sEnd of the deletion some sort of Begin of the insertionfollow-up</p></td><td class="op-uc-table--cell"><p class="op-uc-p">YES, same as above. Especially if I can tag someone else too (offloaded from my mind).</p></td></tr><tr class="op-uc-table--row"><td class="op-uc-table--cell"><p class="op-uc-p"><strong>Actionable list</strong>:End of the insertion Begin of the deletion follow-up

* **Actionable list:**End of the deletion By organising things into individual elements (each that are actionable, or Begin of the insertion"closable"),End of the insertion Begin of the deletion &quot;closable&quot;),End of the deletion it makes it easier to keep track and organise Begin of the insertionquestions</p></td><td class="op-uc-table--cell"><p class="op-uc-p">YES, if different open points related to the same 'object' can be marked with different 'statuses' Done/open), I can get a sense of progress of the whole ("where are we now?").</p></td></tr><tr class="op-uc-table--row"><td class="op-uc-table--cell"><p class="op-uc-p"><strong>Distributed specification</strong>:End of the insertion Begin of the deletion questions

* **Distributed specification:**End of the deletion Because multiple people can identify issues and they become separate threads, single people Begin of the insertiondon'tEnd of the insertion Begin of the deletion don&#39;tEnd of the deletion become Begin of the insertionbottlenecks</p><p class="op-uc-p">NotEnd of the insertion Begin of the deletion bottlenecks.

* When results are visible in one place, easier to find important answers withoutEnd of the deletion necessarily Begin of the insertion"done", but "done for me" = doesn't require my attention anymore</p></td><td class="op-uc-table--cell"><p class="op-uc-p">YES, a bit likeEnd of the insertion Begin of the deletion readingEnd of the deletion the Begin of the insertionproblem specified above (reduce mental load of individual people).</p></td></tr><tr class="op-uc-table--row"><td class="op-uc-table--cell"><p class="op-uc-p"><strong>TrackEnd of the insertion Begin of the deletion whole conversation around it. (But it&#39;s available if someone wants to look it up if needed)

* **TrackEnd of the deletion progress/readiness Begin of the insertionstatus</strong>:End of the insertion Begin of the deletion status:**End of the deletion to mark certain topics as needing attention, Begin of the insertionthat are in the way of something being closed.End of the insertion Begin of the deletion and is there not ready, not &quot;done&quot;.End of the deletion Example: if I could see a little Begin of the insertion"3"End of the insertion Begin of the deletion &quot;3&quot;End of the deletion next to a topic, Begin of the insertionI'dEnd of the insertion Begin of the deletion I&#39;dEnd of the deletion know, there are three resolved issues getting in the way of it being Begin of the insertionclosed.</p></td><td class="op-uc-table--cell"><p class="op-uc-p">YES, a side effect if we're able to easily see how many "open" points are still open.</p></td></tr><tr class="op-uc-table--row"><td class="op-uc-table--cell"><p class="op-uc-p"><strong>ToEnd of the insertion Begin of the deletion closed.

* **ToEnd of the deletion do checked Begin of the insertioneffect</strong>:End of the insertion Begin of the deletion effect:**End of the deletion Seeing threads that are closed would also make me feel better, show me the progress Begin of the insertionI'veEnd of the insertion Begin of the deletion I&#39;veEnd of the deletion made, users feel useful rather than see a bunch of open Begin of the insertionthings.</p><p class="op-uc-p">NotEnd of the insertion Begin of the deletion things.

* NotEnd of the deletion necessarily Begin of the insertion"done", "doneEnd of the insertion Begin of the deletion &quot;done&quot;, &quot;doneEnd of the deletion for Begin of the insertionme"End of the insertion Begin of the deletion me&quot;End of the deletion = Begin of the insertiondoesn'tEnd of the insertion Begin of the deletion doesn&#39;tEnd of the deletion require my attention Begin of the insertionanymore</p></td><td class="op-uc-table--cell"><p class="op-uc-p">YES. Psychologically, always nice to mark something as done/closed.</p></td></tr><tr class="op-uc-table--row"><td class="op-uc-table--cell"><p class="op-uc-p"><strong>Draft</strong>:End of the insertion Begin of the deletion anymore.

* **Draft**:End of the deletion Write something down (perhaps even in a rough form) to not forget it and be able to get back to it in the Begin of the insertionfuture.</p></td><td class="op-uc-table--cell"><p class="op-uc-p">NO, this is private/todo, not something open points can help with.</p></td></tr></tbody></table></figure>

End of the insertion Begin of the deletion future.


End of the deletion ## **Feature ideas**

Interesting ideas that we think might improve current workflow/experience

Begin of the insertion<figure class="table op-uc-figure_align-center op-uc-figure"><table class="op-uc-table"><thead class="op-uc-table--head"><tr class="op-uc-table--row"><th class="op-uc-table--cell op-uc-table--cell_head"><p class="op-uc-p"><strong>Item</strong></p></th><th class="op-uc-table--cell op-uc-table--cell_head"><p class="op-uc-p"><strong>Remarks</strong></p></th></tr></thead><tbody><tr class="op-uc-table--row"><td class="op-uc-table--cell"><p class="op-uc-p"><strong>Snoozing</strong>:End of the insertion Begin of the deletion * **Snoozing:**End of the deletion When I know that something requires my attention, but Begin of the insertionit'sEnd of the insertion Begin of the deletion it&#39;sEnd of the deletion not immediate (but I also Begin of the insertiondon'tEnd of the insertion Begin of the deletion don&#39;tEnd of the deletion want to lose Begin of the insertiontrackEnd of the insertion Begin of the deletion trakcEnd of the deletion of it): Option to add a reminder to a thread (eg. Begin of the insertion"RemindEnd of the insertion Begin of the deletion &quot;RemindEnd of the deletion me next Begin of the insertionweek").</p></td><td class="op-uc-table--cell"><p class="op-uc-p"></p></td></tr><tr class="op-uc-table--row"><td class="op-uc-table--cell"><p class="op-uc-p"><strong>Better facilitating</strong>:End of the insertion Begin of the deletion week&quot;).

* **Better facilitating:**End of the deletion I can define what needs to be discussed, and also get to a Begin of the insertioncertainEnd of the insertion Begin of the deletion certianEnd of the deletion finality or closures (decision/discussion/add to second Begin of the insertionmeeting/ignore).</p></td><td class="op-uc-table--cell"><p class="op-uc-p"></p></td></tr><tr class="op-uc-table--row"><td class="op-uc-table--cell"><p class="op-uc-p"><strong>IEnd of the insertion Begin of the deletion meeting/ignore).

* IEnd of the deletion can then easily identify/know if there Begin of the insertionisn'tEnd of the insertion Begin of the deletion _isn&#39;t_End of the deletion a Begin of the insertionclosure.</strong></p></td><td class="op-uc-table--cell"><p class="op-uc-p"></p></td></tr><tr class="op-uc-table--row"><td class="op-uc-table--cell"><p class="op-uc-p"><strong>Timer/time-boxing</strong>:End of the insertion Begin of the deletion closure.

* **Timer/time-boxing**:End of the deletion items are timed, when the previous one is closed, it triggers the timer for the next Begin of the insertionone.</p></td><td class="op-uc-table--cell"><p class="op-uc-p"></p></td></tr><tr class="op-uc-table--row"><td class="op-uc-table--cell"><p class="op-uc-p"><strong>Democratisation/Voting</strong>:End of the insertion Begin of the deletion one.

* **Democratisation/Voting**:End of the deletion Each participant gets to pick 3 items (or has 3 votes that can be distributed amongst multiple Begin of the insertionitems).</p></td><td class="op-uc-table--cell"><p class="op-uc-p"></p></td></tr><tr class="op-uc-table--row"><td class="op-uc-table--cell"><p class="op-uc-p"><strong>Checkmark (done)</strong>:End of the insertion Begin of the deletion items).

* **Checkmark** (done):End of the deletion Like in GitHub issues, makes it easy to mark things are done or not needing my attention anymore. (Personal, not on my desk Begin of the insertionanymore)</p></td><td class="op-uc-table--cell"><p class="op-uc-p"></p></td></tr><tr class="op-uc-table--row"><td class="op-uc-table--cell"><p class="op-uc-p"><strong>Decision:</strong> In a meeting, create a sub-task and assign it to someone. Concrete way to define follow-up actions to a decision that is taken.</p></td><td class="op-uc-table--cell"><p class="op-uc-p"></p></td></tr><tr class="op-uc-table--row"><td class="op-uc-table--cell"><ul class="op-uc-list"><li class="op-uc-list--item"><p class=" op-uc-p"><strong>Better diffs/previews</strong> of changes withing the work package description or any other custom field of type long text (Careful: this is technically a difficult/complex topic).</p></li><li class="op-uc-list--item"><p class=" op-uc-p">I want to understand easier if I should check/review/follow-up upon a change to a long text (typo fixes vs. significant changes)</p></li></ul></td><td class="op-uc-table--cell"><p class="op-uc-p"></p></td></tr><tr class="op-uc-table--row"><td class="op-uc-table--cell"><ul class="op-uc-list"><li class="op-uc-list--item"><p class=" op-uc-p">The messaging part is <strong>analogue to chat applications</strong>:</p></li><li class="op-uc-list--item"><p class=" op-uc-p">always have the input field for comments visible and sitting at the bottom.</p></li><li class="op-uc-list--item"><p class=" op-uc-p">The order of the activity log should be with the oldest at the top and and the newest visible and directly above the input field.</p></li><li class="op-uc-list--item"><p class=" op-uc-p">Messages by people have a prominent, clear avatar. They are alive/lively.</p></li><li class="op-uc-list--item"><p class=" op-uc-p">Consecutive messages by the same person might get grouped if they belong to the same "message burst", e.g. within the aggregation time. Still, every message that was send is separately identifiable.</p></li></ul></td><td class="op-uc-table--cell"><p class="op-uc-p"></p></td></tr><tr class="op-uc-table--row"><td class="op-uc-table--cell"><ul class="op-uc-list"><li class="op-uc-list--item"><p class=" op-uc-p">Logging other events (status changes, scheduling, custom fields, ...)</p><ul class="op-uc-list"><li class="op-uc-list--item"><p class=" op-uc-p">Attribute changes and their causes, e.g. through scheduling through a relationship, are somewhat more passive than messages. Visually they can blur into the background</p></li></ul></li></ul></td><td class="op-uc-table--cell"><p class="op-uc-p"></p></td></tr><tr class="op-uc-table--row"><td class="op-uc-table--cell"><ul class="op-uc-list"><li class="op-uc-list--item"><p class=" op-uc-p"><strong>Better diffs/previews</strong> of changes withing the work package description or any other custom field of type long text (Careful: this is technically a difficult/complex topic).</p><ul class="op-uc-list"><li class="op-uc-list--item"><p class=" op-uc-p">I want to understand easier if I should check/review/follow-up upon a change to a long text (typo fixes vs. significant changes)</p></li></ul></li></ul></td><td class="op-uc-table--cell"><p class="op-uc-p"></p></td></tr><tr class="op-uc-table--row"><td class="op-uc-table--cell"><ul class="op-uc-list"><li class="op-uc-list--item"><p class=" op-uc-p"><strong>Better diffs/previews</strong> of changes withing the work package description or any other custom field of type long text (Careful: this is technically a difficult/complex topic).</p><ul class="op-uc-list"><li class="op-uc-list--item"><p class=" op-uc-p">I want to understand easier if I should check/review/follow-up upon a change to a long text (typo fixes vs. significant changes)</p></li></ul></li></ul></td><td class="op-uc-table--cell"><p class="op-uc-p"></p></td></tr><tr class="op-uc-table--row"><td class="op-uc-table--cell"><ul class="op-uc-list"><li class="op-uc-list--item"><p class=" op-uc-p"><strong>Reply to message (Clear context communication):</strong></p><ul class="op-uc-list"><li class="op-uc-list--item"><p class=" op-uc-p">On a message hit "Reply" and the message input field indicates that this relates that message.</p></li><li class="op-uc-list--item"><p class=" op-uc-p">When there is a text selected while hitting "Reply" that context gets cited so that it becomes even clearer to which part of a message on is replying to. (That might be similar to adding a comment thread to a word selection inside a long text although there you have a full fledged thread.)</p></li></ul></li></ul></td><td class="op-uc-table--cell"><p class="op-uc-p"></p></td></tr></tbody></table></figure>

End of the insertion Begin of the deletion anymore)


End of the deletion ## **Usage scenarios**

**Task**: Imagine scenarios (temporal/procedural), where an open points feature would improve your life. Use the following format:

> When I...
> I want...
> So that...

<figure class="table op-uc-figure_align-center op-uc-figure"><table class="op-uc-table"><thead class="op-uc-table--head"><tr class="op-uc-table--row"><th class="op-uc-table--cell op-uc-table--cell_head"><p class="op-uc-p"><strong>When I</strong></p></th><th class="op-uc-table--cell op-uc-table--cell_head"><p class="op-uc-p"><strong>I want</strong></p></th><th class="op-uc-table--cell op-uc-table--cell_head"><p class="op-uc-p"><strong>So that</strong></p></th><th class="op-uc-table--cell op-uc-table--cell_head"><p Begin of the insertionclass="op-uc-p">Would I use OpenPoints in this scenario?</p></th></tr></thead><tbody><trEnd of the insertion Begin of the deletion class="op-uc-p">Existing FEATURE requests</p></th></tr></thead><tbody><trEnd of the deletion class="op-uc-table--row"><td class="op-uc-table--cell"><p class="op-uc-p"><strong>When I</strong> am writing specs for a feature and am unsure about a certain behaviour</p></td><td class="op-uc-table--cell"><p class="op-uc-p"><strong>I want</strong> to be able to note down that question and tag a relevant person</p></td><td class="op-uc-table--cell"><p class="op-uc-p"><strong>So that</strong> I can continue working on other things, forget about it for now, and easily get back to the uncertain topic at a later Begin of the insertiontime when that person will have responded.</p></td><tdEnd of the insertion Begin of the deletion time.</p></td><tdEnd of the deletion class="op-uc-table--cell"><p Begin of the insertionclass="op-uc-p">YES.&nbsp;</p></td></tr><trEnd of the insertion Begin of the deletion class="op-uc-p"></p></td></tr><trEnd of the deletion class="op-uc-table--row"><td class="op-uc-table--cell"><p class="op-uc-p"><strong>When I</strong> am in a meeting and topics come up that are interesting, but that we don't have time to discuss at the moment</p></td><td class="op-uc-table--cell"><p class="op-uc-p"><strong>I want</strong> to be able to write them down</p></td><td class="op-uc-table--cell"><p class="op-uc-p"><strong>So that</strong> we can move on without ignoring the issues, but that we don't actually forget about it, and there's a concrete step.</p></td><td class="op-uc-table--cell"><p Begin of the insertionclass="op-uc-p">YES. Create open point, tag somebody related to the current topic/work package or add it to the next iteration of the meeting, move on.</p></td></tr><trEnd of the insertion Begin of the deletion class="op-uc-p"></p></td></tr><trEnd of the deletion class="op-uc-table--row"><td class="op-uc-table--cell"><p class="op-uc-p"><strong>When I</strong> receive a notification on a topic I'm working on that requires multiple decisions Begin of the insertionfromEnd of the insertion Begin of the deletion formEnd of the deletion my side</p></td><td class="op-uc-table--cell"><p class="op-uc-p"><strong>I want</strong> to divide these decisions and organise the timeline for me to work on them</p></td><td class="op-uc-table--cell"><p class="op-uc-p"><strong>So that</strong> I have a clear sense of structure and priority in my workday.</p></td><td class="op-uc-table--cell"><p Begin of the insertionclass="op-uc-p">NO. This is a known challenge for notification management/personal scheduling.</p></td></tr><trEnd of the insertion Begin of the deletion class="op-uc-p"></p></td></tr><trEnd of the deletion class="op-uc-table--row"><td class="op-uc-table--cell"><p class="op-uc-p"><strong>When I</strong> write a message on a certain topic, and I know that the other person is acting on it right now</p></td><td class="op-uc-table--cell"><p class="op-uc-p"><strong>I want</strong> to be aware of this</p></td><td class="op-uc-table--cell"><p class="op-uc-p"><strong>So that</strong> I can stay with the topic and save a costly context switch in my head.</p></td><td class="op-uc-table--cell"><p Begin of the insertionclass="op-uc-p">Need more discussion/clarification.<br><br><s>NO. Open points can't address the notification bit. I need concurrent editing/responding notification so I can stay on.</s></p></td></tr><trEnd of the insertion Begin of the deletion class="op-uc-p"></p></td></tr><trEnd of the deletion class="op-uc-table--row"><td class="op-uc-table--cell"><p class="op-uc-p"><strong>When I</strong> interact with a message that I just received</p></td><td class="op-uc-table--cell"><p class="op-uc-p"><strong>I want</strong> to communicate/not give the expectation that I want to answer it immediately, but that I'll get back to it eventually</p></td><td class="op-uc-table--cell"><p class="op-uc-p"><strong>So that</strong> this does not create false expectations between me and the other people, and that there's a process that both can trust.</p></td><td class="op-uc-table--cell"><p class="op-uc-p"></p></td></tr><tr class="op-uc-table--row"><td class="op-uc-table--cell"><p class="op-uc-p"><strong>When I</strong> want to get an overview of lack of clarity that's slowing down work within the scope of a release, a version, a phase...</p></td><td class="op-uc-table--cell"><p class="op-uc-p"><strong>I want</strong> to be able to quickly see the actual issues that need resolving</p></td><td class="op-uc-table--cell"><p class="op-uc-p"><strong>So that</strong> I get a better sense of what the blocks are and what we can do about it.</p></td><td class="op-uc-table--cell"><p class="op-uc-p"></p></td></tr><tr class="op-uc-table--row"><td class="op-uc-table--cell"><p class="op-uc-p"><strong>When I</strong> have a number of different questions, on a number of different topics for the same person</p></td><td class="op-uc-table--cell"><p class="op-uc-p"><strong>I want</strong> to be able to write down those questions (and tag the relevant person) and then easily access that list later</p></td><td class="op-uc-table--cell"><p class="op-uc-p"><strong>So that</strong> when I have a meeting with that person, we can go through the questions and address them one by one (almost like an automatic agenda list for my meeting).</p></td><td class="op-uc-table--cell"><p class="op-uc-p"></p></td></tr><tr class="op-uc-table--row"><td class="op-uc-table--cell"><p class="op-uc-p"><strong>When I</strong> am working on an external tool (like Figma), and I am taking a decision that needs to be reflected in a work package</p></td><td class="op-uc-table--cell"><p class="op-uc-p"><strong>I want</strong> to bring this decision need into OpenProject</p></td><td class="op-uc-table--cell"><p class="op-uc-p"><strong>So that</strong> the person who needs to make that decision is informed about it, so I know that the item doesn't get lost/ignored.</p></td><td class="op-uc-table--cell"><p class="op-uc-p"></p></td></tr><tr class="op-uc-table--row"><td class="op-uc-table--cell"><p class="op-uc-p"><strong>When I</strong> am in a conversation with someone where a decision has been taken</p></td><td class="op-uc-table--cell"><p class="op-uc-p"><strong>I want</strong> to have this be noted down somewhere, ideally with an existing place where the topic lives (e.g., work package)</p></td><td class="op-uc-table--cell"><p class="op-uc-p"><strong>So that</strong> other people who might be working on this topic are informed, aware of this decision without my needing to manually communicate this to them (time-consuming).</p></td><td class="op-uc-table--cell"><p class="op-uc-p"></p></td></tr><tr class="op-uc-table--row"><td class="op-uc-table--cell"><p class="op-uc-p"><strong>When I</strong> see there's a decision that I'm not entirely happy with (because we've not discussed it properly, given it enough time, or considered important topics)</p></td><td class="op-uc-table--cell"><p class="op-uc-p"><strong>I want</strong> to document reservations or questions that were ignored</p></td><td class="op-uc-table--cell"><p class="op-uc-p"><strong>So that</strong> I don't feel like important topics that were ignored are forgotten ("I told you so") and those topics can be addressed at a later date ("let's handle this later if needed").</p></td><td class="op-uc-table--cell"><p class="op-uc-p"></p></td></tr><tr class="op-uc-table--row"><td class="op-uc-table--cell"><p class="op-uc-p"><strong>When I</strong> want to express a complex thought</p></td><td class="op-uc-table--cell"><p class="op-uc-p"><strong>I want</strong> to have the space to write, add drawings, annotate with other objects like sound, etc.</p></td><td class="op-uc-table--cell"><p class="op-uc-p"><strong>So that</strong> I can clearly express my thoughts without structural limits.</p></td><td class="op-uc-table--cell"><p class="op-uc-p"></p></td></tr><tr class="op-uc-table--row"><td class="op-uc-table--cell"><p class="op-uc-p"><strong>When I</strong> am working on my daily tasks and going on my lovely day</p></td><td class="op-uc-table--cell"><p class="op-uc-p"><strong>I want</strong> to know if my attention is requested by someone or some topic</p></td><td class="op-uc-table--cell"><p class="op-uc-p"><strong>So that</strong> when I address it, I know it's done and off my plate (and I can go skateboarding).</p></td><td class="op-uc-table--cell"><p class="op-uc-p"></p></td></tr><tr class="op-uc-table--row"><td class="op-uc-table--cell"><p class="op-uc-p"><strong>When I</strong> work on a topic and I discover that there are sub-topics that we need to work on separately (or in parallel)</p></td><td class="op-uc-table--cell"><p class="op-uc-p"><strong>I want</strong> to quickly be able to break it down and document that structure</p></td><td class="op-uc-table--cell"><p class="op-uc-p"><strong>So that</strong> I can turn a big topic into manageable chunks that can then be assigned to different people and reveal/express the complexity that we've identified.</p></td><td class="op-uc-table--cell"><p Begin of the insertionclass="op-uc-p">##54730</p></td></tr><tr class="op-uc-table--row"><td class="op-uc-table--cell"><p class="op-uc-p"><strong>When I</strong> have points that require my team's attention</p></td><td class="op-uc-table--cell"><p class="op-uc-p"><strong>I want</strong> to list them all in one place and mark them as open</p></td><td class="op-uc-table--cell"><p class="op-uc-p"><strong>So that</strong> they can be claimed by who ever in the team has more time</p></td><td class="op-uc-table--cell"><p class="op-uc-p"></p></td></tr><tr class="op-uc-table--row"><td class="op-uc-table--cell"><p class="op-uc-p"><strong>When I</strong> have a specific point within a work package that requires a colleague's attention</p></td><td class="op-uc-table--cell"><p class="op-uc-p"><strong>I want</strong> to be able to mark just that bit as "incomplete" somehow and assign it to them</p></td><td class="op-uc-table--cell"><p class="op-uc-p"><strong>So that</strong> I don't have to have that bit of uncertainly affect the entire status of the work package itself (which can then reflect its <i>actual</i> status)</p></td><td class="op-uc-table--cell"><p class="op-uc-p"></p></td></tr></tbody></table></figure>End of the insertion Begin of the deletion class="op-uc-p">##54730</p></td></tr></tbody></table></figure>End of the deletion