A workflow question for anyone who writes posts with others, at work or in an open-source project.
In many teams, feedback on a draft ends up in four places: chat, email, a shared doc and somebody’s memory of a call. The person who schedules the post has to stitch it together.
We built comments-on-drafts into GPTpost because of exactly this: the discussion stays attached to the post through approval. But tools are only half of it. Habits we have found useful:
- specific comments (“too long for Bluesky”) over vague ones
- reply when the change is made
- one-line summary for anything decided in a call
How does your team or project handle this? Especially curious about volunteer projects where people review in their spare time.
You must log in or register to comment.
