Remote Work Tools for Project Management

🗞️ Just out! Latest from our NATO Strategic Communications Centre of Excellence ! “Democratising Data Integration” 🔹Examines the need for standardised data integration and communication protocols in NATO’s strategic information environment. 🔹 Core argument : while advanced data processing tools exist, the lack of standardised integration protocols limits efficiency, security, and rapid decision-making. 🔹Highlights the challenges of fragmented data systems, interoperability issues, and inconsistent data-sharing methodologies across allied organisations. Key Challenges 1. Metadata Standardisation – Inconsistencies in metadata structures lead to misinterpretations and operational inefficiencies. 2. Security Classifications – Differing classification methods create access restrictions, limiting data-sharing effectiveness. 3. Institutional Divergence – NATO allies use various data-sharing protocols, impeding interoperability. 4. Technical Expertise Gaps – The shortage of skilled personnel slows the adoption of modern integration frameworks. 5. Resource Constraints – Budgetary limitations restrict the transition to scalable and secure data systems. 6. Privacy and Compliance Issues – Conflicting regulations (e.g., GDPR) create legal and operational barriers. Proposed Solutions 🔹The report proposes adopting standardised communication protocols to ensure seamless interoperability. Frameworks like Federated Mission Networking (FMN) and VAULTIS are highlighted as potential models for structured data sharing. AI-driven solutions, automated classification systems, and improved governance mechanisms are recommended to enhance operational efficiency. Standardisation would lead to: 🔹Improved Strategic Communications – Faster, more reliable data-driven decision-making. 🔹Operational Efficiency – Reduced manual processing, better crisis response. 🔹Cost-Effectiveness – Lower integration costs through streamlined interoperability.

When I first started in communications, internal and external messaging lived in two separate worlds, but wow, has that changed. If you’re navigating this evolving landscape, here are a few strategies that have worked for me: 🧩 Integration: Align your internal and external channels to create a unified message across the board. 💪 Consistency: Build trust by delivering communications on a predictable schedule. 🔨 Utility: Repurpose your existing tools in innovative ways to tackle multiple communications goals. 🤝 Engagement: Make even the smallest details engaging to keep your audience interested. 🎨 Creativity: Strive to balance informative content with creative storytelling that resonates. Today, “#mixternal” communications or integrating internal and external communications to reinforce a company’s message is the new path forward. Don’t forget, your colleagues are one of your most important audiences—and biggest advocates externally.

Streamline Your New Hire Journey with SAP SuccessFactors Onboarding SAP SuccessFactors Onboarding is more than just an orientation tool—it's a pivotal solution that connects seamlessly with other modules to ensure new hires feel supported from day one. Here's how it integrates with key modules: 👉 Recruiting: Automatically transition candidates into the onboarding process directly from their application. 👉 Employee Central: Facilitate smooth conversion of candidates into employees, whether or not they're sourced via Recruiting. 👉 Learning: Assign courses to new hires even before their first day, ensuring they hit the ground running. 👉 Performance & Goals: Empower employees by setting goals as part of their onboarding journey with templates for New Hire Goal Management. 👉 DocuSign: Enable digital signatures for forms, ensuring compliance and ease across devices. 👉 Qualtrics Employee Lifecycle: Collect actionable feedback through automated surveys triggered upon program completion. Opportunities for Enhanced Integrations: There are potential areas to amplify the onboarding experience: 👉 ITSM tools like ServiceNow: Automate provisioning of equipment and systems access for new employees. What integrations do you think are essential for a next-gen onboarding process? Share your thoughts below! 👇 #SAPSuccessFactors #Onboarding #HRTech #EmployeeExperience #Integration

Ever wondered, how Google Docs allows multiple people to edit the doc, that too in almost real-time while keeping a consistent state? 1. This is a common problem with any collaborative platform. There are multiple people — reading/writing and they might be editing at the same location of the document. How do we solve this issue? 2. One simple thing that comes into mind, is to create a lock on the document when a person is editing and prevent others from making any change during this time. This is a common approach, but this results in a loss of performance and the platform is not completely collaborative. 3. Another approach could be to maintain logs of changes made by each person, along with the timestamp, and use those to build the final state of the document. But, what happens if two people perform the operation at the exactly same time? 4. The problem is similar to resolving conflicts during a git merge, but this has to be done automatically without user intervention. 5. Google uses a collaborative protocol to provide near real-time collaboration on google docs. All the clients(our browsers) interact with the Google docs server and perform the required edits. 6. The clients keep a state of 4 things:1) changes present locally but not sent to the server. 2) the most recent version of the doc sent by the server 3) changes sent to the server but not acknowledged by the server 4) the current version of the doc visible to the user. 7. The servers keep a state of 3 things: 1)current state of doc for the server 2) changes it has received but not acknowledged 3) logs of changes applied. 8) Whenever a client receives an edit from the server, it performs changes on the current state of the document by applying operational transform on the changes which the client has not sent to the server and the ones not acknowledged by the server. To understand in detail: https://lnkd.in/e4M45hG7 You can also visualise it here: https://lnkd.in/ga2_AJsW

𝗜𝗻𝘁𝗲𝗴𝗿𝗮𝘁𝗶𝗻𝗴 𝗖𝗹𝗼𝘂𝗱-𝗡𝗮𝘁𝗶𝘃𝗲 𝗔𝗿𝗰𝗵𝗶𝘁𝗲𝗰𝘁𝘂𝗿𝗲𝘀 𝘄𝗶𝘁𝗵 𝗟𝗲𝗴𝗮𝗰𝘆 𝗦𝘆𝘀𝘁𝗲𝗺𝘀: 𝗟𝗲𝘀𝘀𝗼𝗻𝘀 𝗳𝗿𝗼𝗺 𝘁𝗵𝗲 𝗙𝗶𝗲𝗹𝗱 In a recent engagement with a large financial services company, the goal was ambitious: 𝗺𝗼𝗱𝗲𝗿𝗻𝗶𝘇𝗲 𝘀𝘆𝘀𝘁𝗲𝗺𝘀 𝗼𝗳 𝗲𝗻𝗴𝗮𝗴𝗲𝗺𝗲𝗻𝘁 𝘁𝗼 𝗽𝗿𝗼𝘃𝗶𝗱𝗲 𝗮 𝗰𝘂𝘁𝘁𝗶𝗻𝗴-𝗲𝗱𝗴𝗲 𝗰𝘂𝘀𝘁𝗼𝗺𝗲𝗿 𝗲𝘅𝗽𝗲𝗿𝗶𝗲𝗻𝗰𝗲. 𝙏𝙝𝙚 𝙘𝙖𝙩𝙘𝙝? Much of the critical functionality resided on mainframes—reliable but inflexible systems deeply embedded in their operations. They needed to innovate without sacrificing the stability of their legacy infrastructure. Many organizations face this challenge as they 𝗯𝗮𝗹𝗮𝗻𝗰𝗲 𝗺𝗼𝗱𝗲𝗿𝗻 𝗰𝗹𝗼𝘂𝗱-𝗻𝗮𝘁𝗶𝘃𝗲 𝗮𝗿𝗰𝗵𝗶𝘁𝗲𝗰𝘁𝘂𝗿𝗲𝘀 𝘄𝗶𝘁𝗵 𝗹𝗲𝗴𝗮𝗰𝘆 systems. While cloud-native solutions promise scalability and agility, legacy systems remain indispensable for core processes. Successfully integrating these two requires overcoming issues like 𝗴𝗼𝘃𝗲𝗿𝗻𝗮𝗻𝗰𝗲, 𝗰𝗼𝗻𝘁𝗿𝗼𝗹, and 𝗰𝗼𝗺𝗽𝗮𝘁𝗶𝗯𝗶𝗹𝗶𝘁𝘆 𝗴𝗮𝗽𝘀. Drawing from that experience and others, here are 📌 𝟯 𝗯𝗲𝘀𝘁 𝗽𝗿𝗮𝗰𝘁𝗶𝗰𝗲𝘀 I’ve found valuable when integrating legacy functionality with cloud-based services: 𝟭 | 𝗔𝗱𝗼𝗽𝘁 𝗮 𝗛𝘆𝗯𝗿𝗶𝗱 𝗠𝗼𝗱𝗲𝗹 Transition gradually by adopting hybrid architectures. Retain critical legacy functions on-premises while deploying new features to the cloud, allowing both environments to work in tandem. 𝟮 | 𝗟𝗲𝘃𝗲𝗿𝗮𝗴𝗲 𝗔𝗣𝗜𝘀 𝗮𝗻𝗱 𝗠𝗶𝗰𝗿𝗼𝘀𝗲𝗿𝘃𝗶𝗰𝗲𝘀 Use APIs to expose legacy functionality wherever possible and microservices to orchestrate interactions. This approach modernizes your interfaces without overhauling the entire system. 𝟯 | 𝗨𝘀𝗲 𝗘𝗻𝘁𝗲𝗿𝗽𝗿𝗶𝘀𝗲 𝗔𝗿𝗰𝗵𝗶𝘁𝗲𝗰𝘁𝘂𝗿𝗲 𝗧𝗼𝗼𝗹𝘀 Enterprise architecture tools provide a 𝗵𝗼𝗹𝗶𝘀𝘁𝗶𝗰 𝘃𝗶𝗲𝘄 of your IT landscape, ensuring alignment between cloud and legacy systems. This visibility 𝗵𝗲𝗹𝗽𝘀 𝘆𝗼𝘂 𝗰𝗼𝗺𝗺𝘂𝗻𝗶𝗰𝗮𝘁𝗲 with Product and Leadership to prioritize initiatives and avoid redundancies. Integrating cloud-native architectures with legacy systems isn’t just a technical task—it’s a strategic journey. With the right approach, organizations can unlock innovation while preserving the strengths of their existing infrastructure. _ 👍 Like if you enjoyed this. ♻️ Repost for your network.  ➕ Follow @Kevin Donovan 🔔 _ 🚀 Join Architects' Hub!  Sign up for our newsletter. Connect with a community that gets it. Improve skills, meet peers, and elevate your career! Subscribe 👉 https://lnkd.in/dgmQqfu2 Photo by Raphaël Biscaldi  #CloudNative #LegacySystems #EnterpriseArchitecture #HybridIntegration #APIs #DigitalTransformation

Back when I was a data analyst, I used to “collaborate” by sharing screenshots, exporting Excel files, and sending copies of local ipynb files with teammates. My workflows consisted of hundreds of ad hoc queries in SQL Server scripts or Jupyter Notebook files that were organized by code comments that only made sense to me… And even worse, they were saved as v1, v2, vFinal, etc. in various locations across a disorganized file system that we only cleaned up for archiving purposes only after the project was over 😵💫 I left that job thinking it was normal for a data team to be this unorganized and that data collaboration was overrated—we just need to code and build dashboards better and faster! As I transitioned to companies where data played a much more central role in the company rather than one that was merely an auxiliary function, I learned that collaboration is not just a single thing that data teams have or do not have. There are LEVELS to this: 1️⃣ Synchronous collaboration - At remote-first companies, I needed to be able to work through problems in the same file at the same time alongside my manager when I was stuck ↳ Data tools with real-time code collaboration features that also allow for granular role-based access controls allowed me to prototype rapidly with my virtual teammates 2️⃣ Asynchronous collaboration - I have almost always worked with people across different timezones ↳ Features like commenting and versioning allowed me to pick up work on a project where a colleague left off, and vice versa 3️⃣ Organizational collaboration - All the hard work I did on an analysis was worth nothing if I couldn’t surface the insights to other data teams and business stakeholders and demonstrate the business value ↳ Team workspaces helped us build out dedicated hubs for teams to collaborate efficiently and organize data reports used to share insights interactively A data platform that boasts all of these features and is built with the collaborative data team in mind is JetBrains Datalore. If your data team knows the pain of any of these collaboration struggles, check out Datalore at 👉 https://lnkd.in/gcZSNBeU #ad

In today’s always-on world, downtime isn’t just an inconvenience — it’s a liability. One missed alert, one overlooked spike, and suddenly your users are staring at error pages and your credibility is on the line. System reliability is the foundation of trust and business continuity and it starts with proactive monitoring and smart alerting. 📊 𝐊𝐞𝐲 𝐌𝐨𝐧𝐢𝐭𝐨𝐫𝐢𝐧𝐠 𝐌𝐞𝐭𝐫𝐢𝐜𝐬: 💻 𝐈𝐧𝐟𝐫𝐚𝐬𝐭𝐫𝐮𝐜𝐭𝐮𝐫𝐞: 📌CPU, memory, disk usage: Think of these as your system’s vital signs. If they’re maxing out, trouble is likely around the corner. 📌Network traffic and errors: Sudden spikes or drops could mean a misbehaving service or something more malicious. 🌐 𝐀𝐩𝐩𝐥𝐢𝐜𝐚𝐭𝐢𝐨𝐧: 📌Request/response counts: Gauge system load and user engagement. 📌Latency (P50, P95, P99):  These help you understand not just the average experience, but the worst ones too. 📌Error rates: Your first hint that something in the code, config, or connection just broke. 📌Queue length and lag: Delayed processing? Might be a jam in the pipeline. 📦 𝐒𝐞𝐫𝐯𝐢𝐜𝐞 (𝐌𝐢𝐜𝐫𝐨𝐬𝐞𝐫𝐯𝐢𝐜𝐞𝐬 𝐨𝐫 𝐀𝐏𝐈𝐬): 📌Inter-service call latency: Detect bottlenecks between services. 📌Retry/failure counts: Spot instability in downstream service interactions. 📌Circuit breaker state: Watch for degraded service states due to repeated failures. 📂 𝐃𝐚𝐭𝐚𝐛𝐚𝐬𝐞: 📌Query latency: Identify slow queries that impact performance. 📌Connection pool usage: Monitor database connection limits and contention. 📌Cache hit/miss ratio: Ensure caching is reducing DB load effectively. 📌Slow queries: Flag expensive operations for optimization. 🔄 𝐁𝐚𝐜𝐤𝐠𝐫𝐨𝐮𝐧𝐝 𝐉𝐨𝐛/𝐐𝐮𝐞𝐮𝐞: 📌Job success/failure rates: Failed jobs are often silent killers of user experience. 📌Processing latency: Measure how long jobs take to complete. 📌Queue length: Watch for backlogs that could impact system performance. 🔒 𝐒𝐞𝐜𝐮𝐫𝐢𝐭𝐲: 📌Unauthorized access attempts: Don’t wait until a breach to care about this. 📌Unusual login activity: Catch compromised credentials early. 📌TLS cert expiry: Avoid outages and insecure connections due to expired certificates. ✅𝐁𝐞𝐬𝐭 𝐏𝐫𝐚𝐜𝐭𝐢𝐜𝐞𝐬 𝐟𝐨𝐫 𝐀𝐥𝐞𝐫𝐭𝐬: 📌Alert on symptoms, not causes. 📌Trigger alerts on significant deviations or trends, not only fixed metric limits. 📌Avoid alert flapping with buffers and stability checks to reduce noise. 📌Classify alerts by severity levels – Not everything is a page. Reserve those for critical issues. Slack or email can handle the rest. 📌Alerts should tell a story : what’s broken, where, and what to check next. Include links to dashboards, logs, and deploy history. 🛠 𝐓𝐨𝐨𝐥𝐬 𝐔𝐬𝐞𝐝: 📌 Metrics collection: Prometheus, Datadog, CloudWatch etc. 📌Alerting: PagerDuty, Opsgenie etc. 📌Visualization: Grafana, Kibana etc. 📌Log monitoring: Splunk, Loki etc. #tech #blog #devops #observability #monitoring #alerts

To keep a virtual team connected, the fix isn’t “more meetings.” It’s shared purpose. Clear alignment. And strategic shots of connection. Thank you to The Globe and Mail and Gobi Kim for featuring me alongside Shannae Ingleton Smith and Justin Raymond in this piece on building culture in distributed and remote teams. 🤔 One of the biggest challenges I see? Distributed and remote teams “transacting” with each other instead of truly collaborating. 🧭 The solution starts with defining how we work together. → That’s why I recommend every team create a Team Working Agreement. Yes, it takes time to develop - but the ROI is real. → In our programs, we’ve seen double-digit increases in clarity, connection, and trust. That kind of alignment pays out dividends. 🗺️ A foundational step in this process? Map your team. → Who’s where? What time zones? Who’s hybrid - and from which office on what days? → This simple exercise builds empathy, reduces friction, and improves coordination. → Want to try it? Get the free mapping tool here: https://lnkd.in/eRTZnVUf 💡 Remote doesn't mean never together. Think of intentional gatherings as a “shot of connection.” → This is one of my favorite analogies from Annie Dean at Atlassian. → Atlassian research shows that just one well-designed in-person gathering can boost connection by 27% - with effects lasting 4-5 months. It’s like an inoculation for team connection. 💥 Case Study: a remote agency Shannae leads a fully remote company, Kensington Grey Agency Inc. She reinvests what could've been spent on an office lease into travel - sending groups of employees to meet clients in-person. This strengthens both external relationships and internal connection. Justin's team at Flexday supports Kensington Grey in building their intentional connection by matching them with a well-resourced office space for the agency members to gather for 2 days each month. 📖 Full article: https://lnkd.in/ervVgwmU 👇 What’s one thing your team does - virtually or in-person - to boost connection?

“Start with performance, before you think about productivity. Understand how much variation you have within the exact same roles. Are there systematic challenges that make it difficult for people to achieve their goals?” – Jiayue (Jenny) He, Founder and CEO, Ergeon. In my latest podcast episode, hear Jenny discuss how they measure productivity at Ergeon, a US-focused construction company, with a workforce distributed across 46 countries. With an engineering, technology, and consulting background, Jenny clarifies how and why they assess productivity for different disciplines such as sales, engineering, and product development. She shares her insights about where and why the unit of productivity must be the team rather than the individual. Jenny explains why performance is critical to evaluate first across several identical roles before productivity can be measured. She talks about onboarding for a fully-remote workforce, which differs depending on the complexity and type of role. Jenny lists top challenges she faces managing a distributed workforce, starting with trust and time zones. She describes the deliberate steps they take to mitigate issues. Listen to Jenny’s enlightening interview about her purposeful approach to tackling and tracking critical metrics that enable her to lead and quickly grow a project-focused, fully-distributed construction company: - Spotify - https://lnkd.in/dFPQvZJW - Apple - https://lnkd.in/dfmQ4YJR - Amazon - https://lnkd.in/dtmPW9_r - TuneIn - https://lnkd.in/dJhFHHB5 #projectmanagement #construction #flexibility #mindset #productivity #measurement #distributedteams #fullyremote #remoteworking #trust #connection #relationships #tracking #performancemanagement

Here's a step-by-step to drastically reduce the deluge of emails between you and your clients/internal team. An absolute GAMECHANGER 👇 Enter: The Collaboration Doc 👏 I’ve stolen this idea from Cal Newport’s podcast Deep Questions. I immediately implemented it with my own clients and they LOVE it. Fundamentally, most people don’t need a response *right now* – they just need to be safe in the knowledge that everything is being taken care of. So all the Collaborative Doc is is a very clean, clearly outlined document that you and your clients and/or your internal teams can use asynchronously to reduce overhead tax. Overhead tax is all the unnecessary (and exhausting) meetings and emails flying back and forth that surround a project. Here’s how to drastically reduce your overhead tax immediately: Step 1: Create a shared document This could be in Notion, Google Docs, Word or whatever works best for you and your client. Make sure your privacy settings are all correct. Step 2: Make it incredibly easy to navigate I have mine split into: 📆 Key Details 📝 Meeting Notes 🧠 Brain Dump Within Brain Dump I’ve further split that into all the key stakeholders so they know exactly where to put their notes. Break this down however you want. They key is that it's all clear and formatted, it looks nice, but it's not overworked. This should be as bare bones as possible. Step 3: Agree a cadence The point here is to reassure your client that you will absolutely refer to their notes. If you have a weekly Wednesday meeting for example, say that you will check all notes first thing on a Tuesday. They can be confident that nothing will go un-reviewed and anything that needs to be actioned before the meeting will be. Meanwhile, you get to be clearer on when you work on each client/project, as everyone has a set cadence. Step 4: Be religious about your collaborative documents This only works if your client has absolute trust that you will keep the document updated and reviewed. Do not let anything slip! WHY THIS WORKS Instead of emailing back and forth, clients put any questions, ideas, notes etc into this one, living document. It helps you to whittle communication down to the essential, increasing the value of your work, your time and the experience your client has (remember it's reducing overhead tax for them, too!) I've done the above example for working with a client, but it works just as well for internal teams, too. It gives everyone more time as people know that things are documented and will be picked up, so there's no need to just fire little things off on slack unless they're actually needed there and then. For both groups, streamlining like this means that you can save time and energy for when a response really is needed right away. Simple, I know, but honestly SUCH a winner. Do you do this already? What problems do you foresee and how would you tweak it?