We needed Worksection most during the active phase of work: from March to September-October 2017. The integration process took about a month.
With WS we:
understood who was doing what:
knew what the task status was:
communicated quickly and effectively:
The key functions were:
projects and project components
Responsible.
Communications.
Deadlines:
documents:
By the way, we integrated Worksection georgia mobile database with one of our tools — Slack. It’s really cool. But we didn’t use the “Reports” function and everything related to financial instruments. We simply didn’t have a connection to it.
Problems with using Worksection
It seems to me that the convenience of using WS depends on approaches and habits. For example, I am used to structuring tasks "top down": the general goal is at the top, projects go down from it, then tasks, and so on. I could not build the entire project in Worksection according to this scheme. I had to use third-party resources to draw and understand the macro-pictures of what was happening. But inside a separate project, everything was simple and logical.
What features of Worksection have proven useful?
-
- Posts: 727
- Joined: Tue Jan 07, 2025 4:28 am