2L Architects & Engineers: Structuring Creativity in Architecture Projects
Architecture surrounds us every day – we see schools, industrial complexes, public spaces, and other constructions. Buildings might seem straightforward, yet they hide countless complex decisions. How should a project be planned? How do sustainability principles affect timelines, budgets, and design choices?
2L Architects and Engineers found the answers with Teamhood – the company needed a solution that would merge all project information into a single system, and strong support was just the beginning of what made Teamhood the right choice.
Giedrė Kličienė, a partner at 2L Architects and Engineers, explained that while the company embraces an agile mindset, construction projects are largely waterfall-based, and Teamhood’s Gantt charts, dependencies, and time-tracking tools help the team plan and monitor each phase and project more precisely.
About 2L Architects & Engineers
2L Architects & Engineers is Lithuanian architecture and engineering studio with over 13 years of experience. From modest beginnings in small-scale renovations and reconstruction works, the firm has grown into a full-scope studio that now manages industrial facilities, educational campuses, public buildings, and complex reconstruction projects.
The team has skilled architects and engineers that are dedicated to sustainable, innovative, and socially responsible design.
Currently, 2L Architects and Engineers is concentrating on three main areas: expanding industrial and production facilities, developing high-quality educational and public spaces, and continuing to deliver reconstruction projects that modernize existing buildings while maintaining their character and purpose.
2L Architects & Engineers: Project Planning
Today, much more time is dedicated to the planning phase at 2L Architects and Engineers. Previously, once a contract was signed, the team would immediately dive into the work. Now, they take a brief pause, involve the team early, and map out the entire project from start to finish. This shift is gradually becoming a deeply rooted practice.
Given the nature of construction projects, planning remains largely waterfall-based. Even if the team sees itself as agile, the reality is that structured, sequential workflows dominate the field. As a result, the Gantt chart remains the backbone of their planning process – and Teamhood has strengthened this approach.
We primarily rely on the Gantt chart. Construction projects tend to be waterfall-based, and although we like to call ourselves an agile company, there is very little agile methodology in planning.
Giedrė Kličienė
In Teamhood, the team uses Gantt charts, dependencies, time tracking, portfolio views, and other tools that enhance clarity, reduce risk, and support more efficient execution across projects.
For 2L Architects, “relearning how to plan” isn’t about reinventing project management – it’s about reshaping long-standing habits. The team has shifted from jumping straight into execution to intentionally slowing down at the start, defining how the entire project will unfold.
They now place greater emphasis on milestones, clearer structure, and more consistent oversight. The Gantt chart – previously a periodic reference point – has become a daily navigation tool, helping the team track phases, spot delays early, and understand when processes need to pause or accelerate.
Planning has also expanded beyond scheduling. Communication, risks, and stakeholder management are now formal parts of every project’s preparation, giving teams a more complete and predictable framework to work within.
It’s not that we are changing planning itself – we are changing our habits. We now dedicate more time to creating the project plan from the very beginning and defining more milestones than before.
—
Giedrė Kličienė
Partner at 2L Architects & Engineers
Choosing Teamhood
The journey toward Teamhood didn’t begin with technology – it began with people. Employees at 2L Architects were the first to raise their hands. While the company had long used a Gantt chart solution, key project data lived in separate places, and it became clear that a unified system was needed.
The search expanded into a full comparison of four different tools – including the widely known Jira. But despite strong competitors, the decision came down to two simple but important priorities: choosing a Lithuanian product and having immediate, reliable support when learning something new.
For a team that was just beginning to rethink how projects should be structured, that support made all the difference. Teamhood’s guidance during setup and adoption became the decisive factor – and the foundation of a partnership that has now lasted more than a year and a half.
Our employees wanted a modern tool and we needed a solution that would merge everything into one system – and strong support from your team was the main reason we chose Teamhood.
—
Giedrė Kličienė
Partner at 2L Architects & Engineers
Implementing Teamhood
When 2L Architects decided to implement Teamhood, the company anticipated that there might be some resistance.
However, because the initiative came directly from employees who saw the need for a better tool, any pushback was minimal and isolated. The larger challenge was helping the team develop new habits, like logging hours consistently.
People don’t naturally start logging hours every day right away – it takes time. But overall, we didn’t experience real resistance, just typical human behavior: forgetting, postponing, not wanting to change immediately.
—
Giedrė Kličienė
Partner at 2L Architects & Engineers
The Features That Matter Most
Teamhood isn’t used the same way by everyone at 2L Architects – and that’s exactly the point. Different roles rely on different parts of the tool, each finding value in the features that support their daily work.
Managers lean heavily on reporting. It helps them spot bottlenecks, understand where teams are thriving, and identify where overload or burnout risks may be forming. For them, visibility is everything.
Project managers live in the Gantt chart. It’s their daily workspace – the place where timelines, dependencies, and progress come together.
Team members gravitate toward kanban boards, time tracking, and everyday task planning. Whether someone meticulously logs their work in 15-minute segments or fills in hours at the end of the day, the system adapts to each style. The only non-negotiable rule: hours must be assigned to the right project stage.
Even with all this activity, the team believes they’re still only using a portion of what Teamhood can offer – but practical adoption is already strong, and the tool has become part of everyone’s daily rhythm.
Different employees value different features, depending on their needs – managers use reports, project managers rely on the Gantt chart, and team members use kanban and time tracking.
—
Giedrė Kličienė
Partner at 2L Architects & Engineers
Looking Ahead
Today, Teamhood is used across the entire company. Everyone – from full-time staff to summer interns – actively engages with the tool. Interns receive access through a free guest license, and their work is fully integrated into ongoing projects.
Everyone uses Teamhood – absolutely everyone. Even interns who join us for the summer get access through the free guest license. Their work becomes part of the overall process.
—
Giedrė Kličienė
Partner at 2L Architects & Engineers
To hear more about 2L Architects’ approach to project management and the lessons they’ve learned along the way, you can listen to Teamhood podcast episode with Giedrė Kličienė.
Share your experiences
We would love to hear about your experiences with Teamhood. Share your stories with us and inspire other project management teams with your practices.
Looking to become more effective with Teamhood? Check out our other client stories or knowledge base for more examples.