How We Work

Remotely

Rosedale works remotely. Most collaboration happens asynchronously, and we protect focus time so people can ship.

When you need a real-time decision, use the overlap window or schedule a quick call. Do not keep threads stuck because “we’ll catch up later.”

Planning

We run work as Kanban with weekly estimation. We update the clients via email/Slack once a week, while every 2 weeks we get on a call to show them what we’ve worked on and what’s coming.

Although our builds don’t necessarily fit a specific 2-week cycle, we should keep the cadence in mind to help our Strategists show progress to our clients.

(this might evolve in the future as we see what works best for our builds and with our clients)

Communication

Because we’re remote, we have explicit expectations for communication.

Daily sync (20 minutes). We meet once per day for a short sync. Each person covers: what they did yesterday, what they will do today, and what is blocked or needs a decision.

Daily written update (Slack). Each person posts one update per day in Slack using the same structure: Yesterday, Today, Callouts, Blockers.

Linear for issue-specific decisions. If a discussion changes the scope, the plan, the acceptance criteria, or the delivery of a specific issue, it goes in the Linear comment thread. This is how we keep the history visible for everyone.

If Slack and Linear conflict on an issue, Linear is the source of truth.

Proactive updates. If you finished work and the next person in the chain is not aware, the work is not really moving. When something is ready for review, when you are unblocked, or when you made a decision that affects delivery, say it clearly and say it where others will see it. Do not assume people will notice.

Working hours and availability

We use a fixed overlap window for live collaboration: 11 AM to 3PM Central Time.

Outside overlap, async is normal. If someone is blocked by you, respond in a reasonable time so work does not stall.

Deadlines, urgent production issues, and time-sensitive releases can require additional coordination outside the overlap window.

Quality and “done”

Quality is a shared bar. “Done” means the work matches the acceptance criteria and is ready for the client to validate.

The detailed “When Work Can Be Considered Done” loop lives in the Build Process section and applies across roles.