•   8 min read

Can't see who is working on what and at what stage the tasks are? Worksection 2.0 helps keep everything under control.

The man­ag­er is ask­ing about the project. What is usu­al­ly done in such cas­es? First, you need to check the task man­ag­er, then recall that some­thing was dis­cussed in Slack, and then check if the file the client is wait­ing for is ready. It turns into an inves­ti­ga­tion of who did what, where, and how, ulti­mate­ly lead­ing to confusion.

A study by ZIP­DO revealed an inter­est­ing fact: 78% of projects face infor­ma­tion frag­men­ta­tion, reduc­ing team pro­duc­tiv­i­ty by about 30%. Addi­tion­al­ly, 60% of delays are not due to the work itself, but because it’s unclear who is doing what and who is respon­si­ble for what.

Trans­paren­cy is cru­cial. When it’s clear at any moment what has been done, what is in progress, and where delays may arise. With­out this, the team spends time not on work, but on fig­ur­ing out sta­tus­es and priorities.

We’ve ensured that in Work­sec­tion 2.0, all of this is vis­i­ble at once. Dash­boards, change his­to­ry, Kan­ban, Gantt charts, and reports show the cur­rent state of the project with­out man­u­al infor­ma­tion gath­er­ing and addi­tion­al requests. Each par­tic­i­pant sees the data they need, while the team works with an up-to-date view of the project in real time.

Where do these ques­tions come from every day?

Ini­tial­ly, the team sim­ply gets used to it, think­ing, Well, it’s some­where, we’ll sort it out lat­er.” Some­one hasn’t updat­ed the sta­tus, some­one for­got to write in the chat that they fin­ished, and it seems like noth­ing ter­ri­ble until these lit­tle things” accu­mu­late to the point where no one under­stands what is actu­al­ly hap­pen­ing with the project.


Data is scattered

Tasks in one tool, dis­cus­sions in Slack, files in Google Dri­ve. To under­stand what stage the project is at, every­thing needs to be col­lect­ed man­u­al­ly. A man­ag­er can­not quick­ly answer a sim­ple ques­tion, a new par­tic­i­pant strug­gles to fig­ure out what’s what, and progress seems unpre­dictable, though in real­i­ty, it’s just disorganized.

Man­u­al control

Instead of work­ing, the team reports what has already been done. The man­ag­er writes clar­i­fi­ca­tions, con­ducts sta­tus meet­ings, and gath­ers reports man­u­al­ly. This dis­tracts from work and cre­ates a sense of con­stant oversight.

The client can­not see the progress

With­out access to up-to-date infor­ma­tion, the client is forced to con­stant­ly check the sta­tus. This leads to more calls, less trust, and the impres­sion that some­thing is being hid­den, when in fact, there’s just nowhere to look.

A team with­out a holis­tic view

When it’s unclear how indi­vid­ual tasks influ­ence the out­come, pri­or­i­ties get lost. This leads to dupli­cat­ed work, over­looked depen­den­cies, and even expe­ri­enced par­tic­i­pants make mis­takes due to a lack of context.

How easy is it to con­trol every­thing in Work­sec­tion 2.0?

Gath­er­ing updates about the project man­u­al­ly is prob­a­bly the most tedious thing you can think of. There­fore, in Work­sec­tion 2.0, we’ve changed this log­ic a bit; now the sys­tem pulls and visu­al­izes every­thing hap­pen­ing in devel­op­ment itself.

View every­thing at once with per­son­al­ized dashboards

Instead of both­er­ing the team with calls every morn­ing ask­ing about the sta­tus of tasks, you can just open the main page. In Work­sec­tion 2.0, the dash­board shows each per­son exact­ly what they need for their work: a prod­uct man­ag­er sees over­all progress and dead­lines, a devel­op­er sees their tasks for today, and a man­ag­er sees the over­all sta­tus of all projects.

The work­space is assem­bled from dis­tinct blocks – wid­gets. You can add them, remove them, rearrange them, or adjust fil­ters to see only use­ful information.



For task man­age­ment, there is a con­ve­nient block Tasks”. Here, all your tasks or your team’s tasks are col­lect­ed. The advan­tage is that you can change the sta­tus, switch assignees, or move dead­lines direct­ly from this screen with­out need­ing to go into each task.



Quick­ly sort­ing out dead­lines is made easy with the wid­get Pri­or­i­ties”. The sys­tem itself iden­ti­fies the most impor­tant tasks across all projects and divides them by colors:
  • crit­i­cal:
  • impor­tant
  • nor­mal
In the morn­ing, it’s imme­di­ate­ly clear what to start the day with.


Track­ing the team’s work­load is aid­ed by the activ­i­ty graph. It shows who worked on tasks and when through­out the week. This makes it clear if some­one is over­whelmed with work while oth­ers have time to help their colleagues.


The glob­al pic­ture of the com­pa­ny is shown by the wid­get Projects”. Here, you can see all active or paused projects with progress indi­ca­tors. You can quick­ly assess what per­cent­age of work has been com­plet­ed for each one.


And if it’s impor­tant for you to keep track of every change, there’s the wid­get Events”. It shows the most recent actions on the project in chrono­log­i­cal order. You will imme­di­ate­ly see if some­one left a com­ment, changed a task’s sta­tus, or uploaded a new file, and you can eas­i­ly jump to the rel­e­vant task.


All this data updates auto­mat­i­cal­ly, so you no longer have to col­lect sta­tus­es man­u­al­ly. Plus, we’ve made sure that most quick actions can be done right from the main screen.

There’s a his­to­ry of changes – no more Who changed the deadline?”

In project work, there’s one truth – things are con­stant­ly chang­ing. Dead­lines shift, new assignees are added, tasks are moved to dif­fer­ent stages, and so on. The prob­lem aris­es because after a week, no one remem­bers why such deci­sions were made in the first place. The con­text sim­ply gets lost.

In Work­sec­tion 2.0, you won’t have to rely on mem­o­ry. The sys­tem auto­mat­i­cal­ly records every­thing from the moment a task is cre­at­ed to any changes in sta­tus­es, pri­or­i­ties, respon­si­ble per­sons, or added files. Com­ments and even time-track­ing records are stored here as well.

For this, there’s a Activ­i­ty” tab in each task block. Every­thing is list­ed in a clear chrono­log­i­cal order – what changed, when, and who did it.


This great­ly sim­pli­fies life for the entire team. For exam­ple, if a new per­son joins the project, they don’t need to run around ask­ing about every­thing. It’s enough to just look at the his­to­ry to under­stand the entire con­text of the work. And most impor­tant­ly, unnec­es­sary argu­ments dis­ap­pear in the team, as every deci­sion is record­ed and can be eas­i­ly verified.

How Kan­ban and Gantt charts help to see cur­rent tasks and plans?

When there are too many tasks, every­one tends not to cel­e­brate. In a plain list, it’s hard to quick­ly deter­mine what is real­ly mov­ing and what is sim­ply stuck in place.

The Kan­ban board shows all work in real time. Tasks are orga­nized in columns Planned”, In Progress”, or Await­ing Approval”. The team imme­di­ate­ly sees the cur­rent state of affairs. If plans change, the sta­tus or assignee can be updat­ed direct­ly on the board by sim­ply drag­ging the card. This helps notice in time where work is pil­ing up and who in the team is overwhelmed.



While Kan­ban shows what is hap­pen­ing now, the Gantt chart helps to under­stand what will hap­pen next.

Tasks in a project are usu­al­ly inter­con­nect­ed and fol­low one anoth­er. If one dead­line is extend­ed, oth­ers auto­mat­i­cal­ly shift, but this is hard to notice in a gen­er­al list. On the Gantt time­line, all these con­nec­tions are vis­i­ble at once.

You see the dura­tion of each task and how the project’s progress aligns with the ini­tial plan. If any stage is delayed, the sys­tem high­lights the risks, allow­ing you to adjust dead­lines or redis­trib­ute efforts before prob­lems with dead­lines arise. As a result, every­one under­stands the work prin­ci­ple, and the man­ag­er sees the over­all pic­ture and acts proactively.

Count­ing actu­al time with time track­ing and reports

Explain­ing to a client or man­age­ment where the week of work went is much eas­i­er when you have exact num­bers rather than approx­i­mate esti­mates. How­ev­er, recall­ing and record­ing hours post-fac­tum is a whole dif­fer­ent story.

And to avoid hav­ing this sep­a­rate con­ver­sa­tion and oth­er issues, in Work­sec­tion 2.0, we made it so that time is record­ed right dur­ing the work on the task. The assignee sim­ply starts the built-in timer or adds worked hours man­u­al­ly, pro­vid­ing a brief com­ment. The infor­ma­tion is imme­di­ate­ly saved with­in the task card. As a result, you clear­ly see how many hours a spe­cif­ic task con­sumed and who worked on it.


When it comes to the end of a project, data col­lec­tion usu­al­ly begins from all over the place to com­pile at least some report. In Work­sec­tion 2.0, there’s no need to com­pile every­thing man­u­al­ly, as the sys­tem auto­mat­i­cal­ly gath­ers all record­ed hours into under­stand­able charts.


You can gen­er­ate a report in just a few min­utes to review the total num­ber of hours for the project, com­pare the planned time to the actu­al, or assess the work­load of each team par­tic­i­pant. This kind of report is easy to export and show to the client, thus elim­i­nat­ing all unnec­es­sary ques­tions about where the bud­get went.

Show­ing the client what they need through the Guest” role

Of course, shar­ing work progress with the client is right, but show­ing them all drafts, finan­cial details, or inter­nal cor­re­spon­dence with var­i­ous dis­cus­sions is def­i­nite­ly not advisable.
How­ev­er, with­out a sense of con­trol, the client will feel anx­ious and may not always trust. And that’s fair, which is why we found a bal­ance by giv­ing con­trol with­out allow­ing it to inter­fere with the team’s work.

In Work­sec­tion 2.0, this is set up through the Guest” role. You decide which part of the project to open. The client will be able to access the sys­tem, see approved tasks, cur­rent sta­tus­es, dead­lines, and final files. They can leave com­ments direct­ly in the task con­text, but all inter­nal process­es: tech­ni­cal tasks, finances, time-track­er notes, and pure­ly team chats remain invis­i­ble to them.


More­over, this also saves a ton of time. The client no longer needs to ask about the project dai­ly, as they can log in at any moment and see the progress for them­selves. The team can calm­ly do their job, main­tain inter­nal dia­logues, with­out being dis­tract­ed by end­less sta­tus updates.

Bring­ing order to tasks with a tab­u­lar view

A reg­u­lar task list can be use­ful for improv­ing team work, but what if there are hun­dreds of tasks? The list becomes lengthy, noth­ing is clear, and every­thing gets lost. We shouldn’t let our­selves sink” into this chaos.

That’s why we cre­at­ed a tab­u­lar view. It gath­ers all tasks into an under­stand­able grid that helps quick­ly ori­ent your­self when you need to scan the entire array of tasks at a glance. You cus­tomize the columns, group tasks by dead­lines, assignees, or statuses.


If you need to update dates or reas­sign tasks to anoth­er col­league, there’s no need to open each card sep­a­rate­ly. All changes can be made direct­ly in the table cells, just like in reg­u­lar Excel. This saves a lot of time when you need to quick­ly tidy up a large vol­ume of work.

You can work even better

The worst part is when half the day goes not to work, but to clar­i­fi­ca­tions like who is doing this” and where is it locat­ed.” This is exhaust­ing for both the team and the managers.

Work­sec­tion 2.0 is exact­ly what’s need­ed to elim­i­nate all unnec­es­sary clut­ter. When sta­tus­es, change his­to­ry, and dead­lines are open and clear, the need to ping each oth­er in mes­sen­gers every hour or gath­er anoth­er call for thir­ty min­utes just to find out the sta­tus of a task disappears.

And it leads to a sim­ple sto­ry, where there’s less mess, less dupli­ca­tion, and much more peace to just do your job.

Switch to Work­sec­tion 2.0 and see how it feels to work with­out unnec­es­sary headaches.


esc
Share
или
PM school
Small businesses don’t shop for project management software because they like software. They shop because something broke. A deadline slipped. A client asked for a status update nobody could answer. Somebody...
2 September 2026   •   22 min read
PM school
Wrike is a genuinely capable project management tool. That’s half the problem. Most teams that leave don’t leave because something broke. They leave because they spent three months configuring folder...
26 August 2026   •   22 min read
PM school
Atlassian finally put a date on it. Jira Data Center — the last self-hosted Jira you could actually buy — goes read-only on March 28, 2029, and the door to new data center subscriptions already shut for...
25 August 2026   •   23 min read