[k3fernan]

My co-founder and I divide our days: before lunch, we take meetings, user interviews, feedback sessions, respond to emails, and tickets. Essentially shallow or synchronous work.

After lunch, we go heads down on coding, design, or writing work. Deep or async work.

This system allows us to always have daily feedback on our product but also uninterrupted time to change the product, every day.

You have to time-box the sync/shallow work, enough to get a good loop in but it's okay if certain things get pushed a day or so. You always have to make space for the deep work.

[tschwimmer]

I think this is a good division but I'd switch the order. Deep work requires concentration that rapidly evaporates later in the day. This varies between people but I find I'm most successful when I put my most difficult and demanding work in the morning.

[Folcon]

I think this might be a morning person / evening person thing. I for example find it much easier to do deep work later in the day.

[data_spy]

I would flip this. I'm personally fresher in the morning and would dedicate that time to coding as it needs more willpower.

[jiux]

Interesting...what made you two decide to go heads down in the afternoon versus morning?