I think all knowledge workers should note what they did at the end of the day - it helps with accountability and gives a sense of achievement. For example a tool like idonethis.com helps you and everyone stay up-to-date and see quickly where problems are. Or ask everyone to just email you at the end of the day or a fixed period. Always read them and respond if needed.
You note that you feel you are slowing your team down - if it's because you are relied on to be building core tasks, try building mock-ups first so they can work. Another good tool is apiary.io if you work with APIs for example: it combines fleshing out your API with actually providing a functional framework so the front-end guys can get to work.
If it's documentation slowing you down, give everyone some days off or get them on another task and catch up. Use paper and pen or whiteboarding or a design tool like Flairbuilder if you need to really understand your ideas before trying to explain them to someone else.
You note that you feel you are slowing your team down - if it's because you are relied on to be building core tasks, try building mock-ups first so they can work. Another good tool is apiary.io if you work with APIs for example: it combines fleshing out your API with actually providing a functional framework so the front-end guys can get to work.
If it's documentation slowing you down, give everyone some days off or get them on another task and catch up. Use paper and pen or whiteboarding or a design tool like Flairbuilder if you need to really understand your ideas before trying to explain them to someone else.